Systems and methods for multi-vehicle adaptive data collection in a network of moving things, for example including autonomous vehicles

ABSTRACT

Systems and methods for optimizing data gathering in a network of moving things. As non-limiting examples, various aspects of this disclosure provide systems and methods for operating sensor systems and collecting data from sensor systems in a network resource-efficient manner

CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE

This patent application makes reference to, claims priority to, andclaims benefit from U.S. Provisional Application Ser. No. 62/253,249,titled “Systems and Methods for Optimizing Data Gathering in a Networkof Moving Things,” filed on Nov. 10, 2015, which is hereby incorporatedherein by reference in its entirety.

The present application is also related to U.S. Provisional ApplicationSer. No. 62/221,997, titled “Integrated Communication Network for aNetwork of Moving Things,” filed on Sep. 22, 2015; U.S. ProvisionalApplication Ser. No. 62/222,016, titled “Systems and Methods forSynchronizing a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,042, titled “Systems and Methodsfor Managing a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,066, titled “Systems and Methodsfor Monitoring a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,077, titled “Systems and Methodsfor Detecting and Classifying Anomalies in a Network of Moving Things,”filed on Sep. 22, 2015; U.S. Provisional Application Ser. No.62/222,098, titled “Systems and Methods for Managing Mobility in aNetwork of Moving Things,” filed on Sep. 22, 2015; U.S. ProvisionalApplication Ser. No. 62/222,121, titled “Systems and Methods forManaging Connectivity a Network of Moving Things,” filed on Sep. 22,2015; U.S. Provisional Application Ser. No. 62/222,135, titled “Systemsand Methods for Collecting Sensor Data in a Network of Moving Things,”filed on Sep. 22, 2015; U.S. Provisional Application Ser. No.62/222,145, titled “Systems and Methods for Interfacing with a Networkof Moving Things,” filed on Sep. 22, 2015; U.S. Provisional ApplicationSer. No. 62/222,150, titled “Systems and Methods for Interfacing with aUser of a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,168, titled “Systems and Methodsfor Data Storage and Processing for a Network of Moving Things,” filedon Sep. 22, 2015; U.S. Provisional Application Ser. No. 62/222,183,titled “Systems and Methods for Vehicle Traffic Management in a Networkof Moving Things,” filed on Sep. 22, 2015; U.S. Provisional ApplicationSer. No. 62/222,186, titled “Systems and Methods for EnvironmentalManagement in a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,190, titled “Systems and Methodsfor Port Management in a Network of Moving Things,” filed on Sep. 22,2015; U.S. Provisional Patent Application Ser. No. 62/222,192, titled“Communication Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/244,8286, titled “UtilizingHistorical Data to Correct GPS Data in a Network of Moving Things,”filed on Oct. 22, 2015; U.S. Provisional Application Ser. No.62/244,930, titled “Using Anchors to Correct GPS Data in a Network ofMoving Things,” filed on Oct. 22, 2015; U.S. Provisional ApplicationSer. No. 62/246,368, titled “Systems and Methods for Inter-ApplicationCommunication in a Network of Moving Things,” filed on Oct. 26, 2015;U.S. Provisional Application Ser. No. 62/246,372, titled “Systems andMethods for Probing and Validating Communication in a Network of MovingThings,” filed on Oct. 26, 2015; U.S. Provisional Application Ser. No.62/250,544, titled “Adaptive Rate Control for Vehicular Networks,” filedon Nov. 4, 2015; U.S. Provisional Application Ser. No. 62/273,878,titled “Systems and Methods for Reconfiguring and Adapting Hardware in aNetwork of Moving Things,” filed on Dec. 31, 2015; U.S. ProvisionalApplication Ser. No. 62/253,249, titled “Systems and Methods forOptimizing Data Gathering in a Network of Moving Things,” filed on Nov.10, 2015; U.S. Provisional Application Ser. No. 62/257,421, titled“Systems and Methods for Delay Tolerant Networking in a Network ofMoving Things,” filed on Nov. 19, 2015; U.S. Provisional ApplicationSer. No. 62/265,267, titled “Systems and Methods for Improving Coverageand Throughput of Mobile Access Points in a Network of Moving Things,”filed on Dec. 9, 2015; U.S. Provisional Application Ser. No. 62/270,858,titled “Channel Coordination in a Network of Moving Things,” filed onDec. 22, 2015; U.S. Provisional Application Ser. No. 62/257,854, titled“Systems and Methods for Network Coded Mesh Networking in a Network ofMoving Things,” filed on Nov. 20, 2015; U.S. Provisional ApplicationSer. No. 62/260,749, titled “Systems and Methods for Improving FixedAccess Point Coverage in a Network of Moving Things,” filed on Nov. 30,2015; U.S. Provisional Application Ser. No. 62/273,715, titled “Systemsand Methods for Managing Mobility Controllers and Their NetworkInteractions in a Network of Moving Things,” filed on Dec. 31, 2015;U.S. Provisional Application Ser. No. 62/281,432, titled “Systems andMethods for Managing and Triggering Handovers of Mobile Access Points ina Network of Moving Things,” filed on Jan. 21, 2016; U.S. ProvisionalApplication Ser. No. 62/268,188, titled “Captive Portal-related Controland Management in a Network of Moving Things,” filed on Dec. 16, 2015;U.S. Provisional Application Ser. No. 62/270,678, titled “Systems andMethods to Extrapolate High-Value Data from a Network of Moving Things,”filed on Dec. 22, 2015; U.S. Provisional Application Ser. No.62/272,750, titled “Systems and Methods for Remote Software Update andDistribution in a Network of Moving Things,” filed on Dec. 30, 2015;U.S. Provisional Application Ser. No. 62/278,662, titled “Systems andMethods for Remote Configuration Update and Distribution in a Network ofMoving Things,” filed on Jan. 14, 2016; U.S. Provisional ApplicationSer. No. 62/286,243, titled “Systems and Methods for Adapting a Networkof Moving Things Based on User Feedback,” filed on Jan. 22, 2016; U.S.Provisional Application Ser. No. 62/278,764, titled “Systems and Methodsto Guarantee Data Integrity When Building Data Analytics in a Network ofMoving Things,” Jan. 14, 2016; U.S. Provisional Application Ser. No.62/286,515, titled “Systems and Methods for Self-Initialization andAutomated Bootstrapping of Mobile Access Points in a Network of MovingThings,” filed on Jan. 25, 2016; U.S. Provisional Application Ser. No.62/295,602, titled “Systems and Methods for Power Management in aNetwork of Moving Things,” filed on Feb. 16, 2016; and U.S. ProvisionalApplication Ser. No. 62/299,269, titled “Systems and Methods forAutomating and Easing the Installation and Setup of the InfrastructureSupporting a Network of Moving Things,” filed on Feb. 24, 2016; each ofwhich is hereby incorporated herein by reference in its entirety for allpurposes.

BACKGROUND

Current communication networks are unable to adequately supportcommunication environments involving moving networks. As a non-limitingexample, current communication networks are unable to adequately supporta network comprising a complex array of both moving and static nodes,some of which may be network access points (e.g., the Internet of movingthings) interacting with sensor systems. Limitations and disadvantagesof conventional methods and systems will become apparent to one of skillin the art, through comparison of such approaches with some aspects ofthe present methods and systems set forth in the remainder of thisdisclosure with reference to the drawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIG. 2 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIG. 3 shows a diagram of a metropolitan area network, in accordancewith various aspects of this disclosure.

FIG. 4 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIGS. 5A-5C show a plurality of network configurations illustrating theflexibility and/or and resiliency of a communication network, inaccordance with various aspects of this disclosure.

FIG. 6 shows a block diagram of an example communication network, inaccordance with various aspects of the present disclosure.

FIG. 7 shows a block diagram of an example communication network, inaccordance with various aspects of the present disclosure.

FIG. 8 shows a flow diagram of an example method of collecting data in anetwork of moving things, in accordance with various aspects of thepresent disclosure.

FIG. 9 shows a block diagram of an example AP system for interfacingwith a sensor system, in accordance with various aspects of the presentdisclosure.

FIG. 10 shows a block diagram of an example AP system for interfacingwith a sensor system, in accordance with various aspects of the presentdisclosure.

FIG. 11 shows a flow diagram of an example method of collecting data ina network of moving things, in accordance with various aspects of thepresent disclosure.

FIG. 12 shows a block diagram of various components of an examplecommunication network, in accordance with various aspects of the presentdisclosure

SUMMARY

Various aspects of this disclosure provide systems and methods foroptimizing data gathering in a network of moving things. As non-limitingexamples, various aspects of this disclosure provide systems and methodsfor operating sensor systems and collecting data from sensor systems ina network resource-efficient manner.

DETAILED DESCRIPTION OF VARIOUS ASPECTS OF THE DISCLOSURE

As utilized herein the terms “circuits” and “circuitry” refer tophysical electronic components (i.e., hardware) and any software and/orfirmware (“code”) that may configure the hardware, be executed by thehardware, and or otherwise be associated with the hardware. As usedherein, for example, a particular processor and memory (e.g., a volatileor non-volatile memory device, a general computer-readable medium, etc.)may comprise a first “circuit” when executing a first one or more linesof code and may comprise a second “circuit” when executing a second oneor more lines of code. Additionally, a circuit may comprise analogand/or digital circuitry. Such circuitry may, for example, operate onanalog and/or digital signals. It should be understood that a circuitmay be in a single device or chip, on a single motherboard, in a singlechassis, in a plurality of enclosures at a single geographical location,in a plurality of enclosures distributed over a plurality ofgeographical locations, etc. Similarly, the term “module” may, forexample, refer to a physical electronic components (i.e., hardware) andany software and/or firmware (“code”) that may configure the hardware,be executed by the hardware, and or otherwise be associated with thehardware.

As utilized herein, circuitry is “operable” to perform a functionwhenever the circuitry comprises the necessary hardware and code (if anyis necessary) to perform the function, regardless of whether performanceof the function is disabled, or not enabled (e.g., by auser-configurable setting, factory setting or trim, etc.).

As utilized herein, “and/or” means any one or more of the items in thelist joined by “and/or”. As an example, “x and/or y” means any elementof the three-element set {(x), (y), (x, y)}. That is, “x and/or y” means“one or both of x and y.” As another example, “x, y, and/or z” means anyelement of the seven-element set {(x), (y), (z), (x, y), (x, z), (y, z),(x, y, z)}. That is, “x, y, and/or x” means “one or more of x, y, andz.” As utilized herein, the terms “e.g.,” and “for example,”“exemplary,” and the like set off lists of one or more non-limitingexamples, instances, or illustrations.

The terminology used herein is for the purpose of describing particularexamples only and is not intended to be limiting of the disclosure. Asused herein, the singular forms are intended to include the plural formsas well, unless the context clearly indicates otherwise. It will befurther understood that the terms “comprises,” “includes,” “comprising,”“including,” “has,” “have,” “having,” and the like when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

It will be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms. These terms are only used to distinguish oneelement from another element. Thus, for example, a first element, afirst component or a first section discussed below could be termed asecond element, a second component or a second section without departingfrom the teachings of the present disclosure. Similarly, various spatialterms, such as “upper,” “lower,” “side,” and the like, may be used indistinguishing one element from another element in a relative manner. Itshould be understood, however, that components may be oriented indifferent manners, for example an electronic device may be turnedsideways so that its “top” surface is facing horizontally and its “side”surface is facing vertically, without departing from the teachings ofthe present disclosure.

With the proliferation of the mobile and/or static things (e.g.,devices, machines, people, etc.) and logistics for such things to becomeconnected to each other (e.g., in the contexts of smart logistics,transportation, environmental sensing, etc.), a platform that is forexample always-on, robust, scalable and secure that is capable ofproviding connectivity, services and Internet access to such things (orobjects), anywhere and anytime is desirable. Efficient power utilizationwithin the various components of such system is also desirable.

Accordingly, various aspects of the present disclosure provide afully-operable, always-on, responsive, robust, scalable, secureplatform/system/architecture to provide connectivity, services andInternet access to all mobile things and/or static things (e.g.,devices, machines, people, access points, end user devices, sensors,etc.) anywhere and anytime, while operating in an energy-efficientmanner.

Various aspects of the present disclosure provide a platform that isflexibly configurable and adaptable to the various requirements,features, and needs of different environments, where each environmentmay be characterized by a respective level of mobility and density ofmobile and/or static things, and the number and/or types of access tothose things. Characteristics of various environments may, for example,include high mobility of nodes (e.g., causing contacts or connections tobe volatile), high number of neighbors, high number of connected mobileusers, mobile access points, availability of multiple networks andtechnologies (e.g., sometimes within a same area), etc. For example, themode of operation of the platform may be flexibly adapted fromenvironment to environment, based on each environment's respectiverequirements and needs, which may be different from other environments.Additionally for example, the platform may be flexibly optimized (e.g.,at design/installation time and/or in real-time) for different purposes(e.g., to reduce the latency, increase throughput, reduce powerconsumption, load balance, increase reliability, make more robust withregard to failures or other disturbances, etc.), for example based onthe content, service or data that the platform provides or handleswithin a particular environment.

In accordance with various aspects of the present disclosure, manycontrol and management services (e.g., mobility, security, routing,etc.) are provided on top of the platform (e.g., directly, using controloverlays, using containers, etc.), such services being compatible withthe services currently deployed on top of the Internet or othercommunication network(s).

The communication network (or platform), in whole or in part, may forexample be operated in public and/or private modes of operation, forexample depending on the use case. The platform may, for example,operate in a public or private mode of operation, depending on theuse-case (e.g., public Internet access, municipal environment sensing,fleet operation, etc.).

Additionally for example, in an implementation in which various networkcomponents are mobile, the transportation and/or signal controlmechanisms may be adapted to serve the needs of the particularimplementation. Also for example, wireless transmission power and/orrate may be adapted (e.g., to mitigate interference, to reduce powerconsumption, to extend the life of network components, etc.

Various example implementations of a platform, in accordance withvarious aspects of the present disclosure, are capable of connectingdifferent subsystems, even when various other subsystems that maynormally be utilized are unavailable. For example, the platform maycomprise various built-in redundancies and fail-recovery mechanisms. Forexample, the platform may comprise a self-healing capability,self-configuration capability, self-adaptation capability, etc. Theprotocols and functions of the platform may, for example, be prepared tobe autonomously and smoothly configured and adapted to the requirementsand features of different environments characterized by different levelsof mobility and density of things (or objects), the number/types ofaccess to those things. For example, various aspects of the platform maygather context parameters that can influence any or all decisions. Suchparameters may, for example, be derived locally, gathered from aneighborhood, Fixed APs, the Cloud, etc. Various aspects of the platformmay also, for example, ask for historical information to feed any of thedecisions, where such information can be derived from historical data,from surveys, from simulators, etc. Various aspects of the platform mayadditionally, for example, probe or monitor decisions made throughoutthe network, for example to evaluate the network and/or the decisionsthemselves in real-time. Various aspects of the platform may further,for example, enforce the decisions in the network (e.g., afterevaluating the probing results). Various aspects of the platform may,for example, establish thresholds to avoid any decision that is to beconstantly or repeatedly performed without any significant advantage(e.g., technology change, certificate change, IP change, etc.). Variousaspects of the platform may also, for example, learn locally (e.g., withthe decisions performed) and dynamically update the decisions.

In addition to (or instead of) failure robustness, a platform mayutilize multiple connections (or pathways) that exist between distinctsub-systems or elements within the same sub-system, to increase therobustness and/or load-balancing of the system.

The following discussion will present examples of the functionalityperformed by various example subsystems of the communication network. Itshould be understood that the example functionality discussed hereinneed not be performed by the particular example subsystem or by a singlesubsystem. For example, the subsystems present herein may interact witheach other, and data or control services may be deployed either in acentralized way, or having their functionalities distributed among thedifferent subsystems, for example leveraging the cooperation between theelements of each subsystem.

Various aspects of the present disclosure provide a communicationnetwork (e.g., a city-wide vehicular network, a shipping port-sizedvehicular network, a campus-wide vehicular network, etc.) that utilizesvehicles (e.g., automobiles, buses, trucks, boats, forklifts,human-operated vehicles, autonomous and/or remote controlled vehicles,etc.) as Wi-Fi hotspots. Note that Wi-Fi is generally used throughoutthis discussion as an example, but the scope of various aspects of thisdisclosure is not limited thereto. For example, other wireless LANtechnologies, PAN technologies, MAN technologies, etc., may be utilized.Such utilization may, for example, provide cost-effective ways to gathersubstantial amounts of urban data, and provide for the efficientoffloading of traffic from congested cellular networks (or othernetworks). In controlled areas (e.g., ports, harbors, etc.) with manyvehicles, a communication network in accordance with various aspects ofthis disclosure may expand the wireless coverage of existing enterpriseWi-Fi networks, for example providing for real-time communication withvehicle drivers (e.g., human, computer-controlled, etc.) and othermobile employees without the need for SIM cards or cellular (or othernetwork) data plans.

Vehicles may have many advantageous characteristics that make themuseful as Wi-Fi (or general wireless) hotspots. For example, vehiclesgenerally have at least one battery, vehicles are generally denselyspread over the city at street level and/or they are able to establishmany contacts with each other in a controlled space, and vehicles cancommunicate with 10× the range of normal Wi-Fi in the 5.9 GHz frequencyband, reserved for intelligent transportation systems in the EU, theU.S., and elsewhere. Note that the scope of this disclosure is notlimited to such 5.9 GHz wireless communication. Further, vehicles areable to effectively expand their coverage area into a swath over aperiod of time, enabling a single vehicle access point to interact withsubstantially more data sources over the period of time.

In accordance with various aspects of the present disclosure, anaffordable multi-network on-board unit (OBU) is presented. Note that theOBU may also be referred to herein as a mobile access point, Mobile AP,MAP, etc. The OBU may, for example, comprise a plurality of networkinginterfaces (e.g., Wi-Fi, 802.11p, 4G, Bluetooth, UWB, etc.). The OBUmay, for example, be readily installed in or on private and/or publicvehicles (e.g., individual user vehicles, vehicles of private fleets,vehicles of public fleets, etc.). The OBU may, for example, be installedin transportation fleets, waste management fleets, law enforcementfleets, emergency services, road maintenance fleets, taxi fleets,aircraft fleets, etc. The OBU may, for example, be installed in or on avehicle or other structure with free mobility or relatively limitedmobility. The OBU may also, for example, be carried by a person orservice animal, mounted to a bicycle, mounted to a moving machine ingeneral, mounted to a container, etc.

The OBUs may, for example, operate to connect passing vehicles to thewired infrastructure of one or more network providers, telecomoperators, etc. In accordance with the architecture, hardware, andsoftware functionality discussed herein, vehicles and fleets can beconnected not just to the cellular networks (or other wide area ormetropolitan area networks, etc.) and existing Wi-Fi hotspots spreadover a city or a controlled space, but also to other vehicles (e.g.,utilizing multi-hop communications to a wired infrastructure, single ormulti-hop peer-to-peer vehicle communication, etc.). The vehicles and/orfleets may, for example, form an overall mesh of communication links,for example including the OBUs and also fixed Access Points (APs)connected to the wired infrastructure (e.g., a local infrastructure,etc.). Note that OBUs herein may also be referred to as “Mobile APs,”“mobile hotspots,” “MAPs,” etc. Also note that fixed access points mayalso be referred to herein as Road Side Units (RSUs), Fixed APs, FAPs,etc.

In an example implementation, the OBUs may communicate with the FixedAPs utilizing a relatively long-range protocol (e.g., 802.11p, etc.),and the Fixed APs may, in turn, be hard wired to the wiredinfrastructure (e.g., via cable, tethered optical link, etc.). Note thatFixed APs may also, or alternatively, be coupled to the infrastructurevia wireless link (e.g., 802.11p, etc.). Additionally, clients or userdevices may communicate with the OBUs using one or more relativelyshort-range protocols (e.g., Wi-Fi, Bluetooth, UWB, etc.). The OBUs, forexample having a longer effective wireless communication range thantypical Wi-Fi access points or other wireless LAN/PAN access points(e.g., at least for links such as those based on 802.11p, etc.), arecapable of substantially greater coverage areas than typical Wi-Fi orother wireless LAN/PAN access points, and thus fewer OBUs are necessaryto provide blanket coverage over a geographical area.

The OBU may, for example, comprise a robust vehicular networking module(e.g., a connection manager) which builds on long-range communicationprotocol capability (e.g., 802.11p, etc.). For example, in addition tocomprising 802.11p (or other long-range protocol) capability tocommunicate with Fixed APs, vehicles, and other nodes in the network,the OBU may comprise a network interface (e.g., 802.11a/b/g/n, 802.11ac,802.11af, any combination thereof, etc.) to provide wireless local areanetwork (WLAN) connectivity to end user devices, sensors, fixed Wi-Fiaccess points, etc. For example, the OBU may operate to providein-vehicle Wi-Fi Internet access to users in and/or around the vehicle(e.g., a bus, train car, taxi cab, public works vehicle, etc.). The OBUmay further comprise one or more wireless backbone communicationinterfaces (e.g., cellular network interfaces, etc.). Though in variousexample scenarios, a cellular network interface (or other wirelessbackbone communication interface) might not be the preferred interfacefor various reasons (e.g., cost, power, bandwidth, etc.), the cellularnetwork interface may be utilized to provide connectivity ingeographical areas that are not presently supported by a Fixed AP, maybe utilized to provide a fail-over communication link, may be utilizedfor emergency communications, may be utilized to subscribe to localinfrastructure access, etc. The cellular network interface may also, forexample, be utilized to allow the deployment of solutions that aredependent on the cellular network operators.

An OBU, in accordance with various aspects of the present disclosure,may for example comprise a smart connection manager that can select thebest available wireless link(s) (e.g., Wi-Fi, 802.11p, cellular, vehiclemesh, etc.) with which to access the Internet. The OBU may also, forexample, provide geo-location capabilities (e.g., GPS, etc.), motiondetection sensors to determine if the vehicle is in motion, and a powercontrol subsystem (e.g., to ensure that the OBU does not deplete thevehicle battery, etc.). The OBU may, for example, comprise any or all ofthe sensors (e.g., environmental sensors, etc.) discussed herein.

The OBU may also, for example, comprise a manager that managesmachine-to-machine data acquisition and transfer (e.g., in a real-timeor delay-tolerant fashion) to and from the Cloud. For example, the OBUmay log and/or communicate information of the vehicles.

The OBU may, for example, comprise a connection and/or routing managerthat operates to perform routing of communications in avehicle-to-vehicle/vehicle-to-infrastructure multi-hop communication. Amobility manager (or controller, MC) may, for example, ensure thatcommunication sessions persist over one or more handoff(s) (alsoreferred to herein as a “handover” or “handovers”) (e.g., betweendifferent Mobile APs, Fixed APs, base stations, hot spots, etc.), amongdifferent technologies (e.g., 802.11p, cellular, Wi-Fi, satellite,etc.), among different MCs (e.g., in a fail-over scenario, loadredistribution scenario, etc.), across different interfaces (or ports),etc. Note that the MC may also be referred to herein as a Local MobilityAnchor (LMA), a Network Controller, etc. Note that the MC, or aplurality thereof, may for example be implemented as part of thebackbone, but may also, or alternatively, be implemented as part of anyof a variety of components or combinations thereof. For example, the MCmay be implemented in a Fixed AP (or distributed system thereof), aspart of an OBU (or a distributed system thereof), etc. Variousnon-limiting examples of system components and/or methods are providedin U.S. Provisional Application No. 62/222,098, filed Sep. 22, 2015, andtitled “Systems and Method for Managing Mobility in a Network of MovingThings,” the entire contents of which are hereby incorporated herein byreference. Note that in an example implementation including a pluralityof MCs, such MCs may be co-located and/or may be geographicallydistributed.

Various aspects of the present disclosure also provide a Cloud-basedservice-oriented architecture that handles the real-time management,monitoring and reporting of the network and clients, the functionalitiesrequired for data storage, processing and management, the Wi-Fi clientauthentication and Captive Portal display, etc.

A communication network (or component thereof) in accordance withvarious aspects of the present disclosure may, for example, support awide range of smart city applications (or controlled scenarios, orconnected scenarios, etc.) and/or use-cases, as described herein.

For example, an example implementation may operate to turn each vehicle(e.g., both public and private taxis, buses, trucks, etc.) into a MobileAP (e.g., a mobile Wi-Fi hotspot), offering Internet access toemployees, passengers and mobile users travelling in the city, waitingin bus stops, sitting in parks, etc. Moreover, through an examplevehicular mesh network formed between vehicles and/or fleets ofvehicles, an implementation may be operable to offload cellular trafficthrough the mobile Wi-Fi hotspots and/or Fixed APs (e.g., 802.11p-basedAPs) spread over the city and connected to the wired infrastructure ofpublic or private telecom operators in strategic places, while ensuringthe widest possible coverage at the lowest possible cost.

An example implementation (e.g., of a communication network and/orcomponents thereof) may, for example, be operable as a massive urbanscanner that gathers large amounts of data (e.g., continuously)on-the-move, actionable or not, generated by a myriad of sourcesspanning from the in-vehicle sensors or On Board Diagnostic System port(e.g., OBD2, etc.), interface with an autonomous vehicle driving system,external Wi-Fi/Bluetooth-enabled sensing units spread over the city,devices of vehicles' drivers and passengers (e.g., informationcharacterizing such devices and/or passengers, etc.), positioning systemdevices (e.g., position information, velocity information, trajectoryinformation, travel history information, etc.), etc.

Depending on the use case, the OBU may for example process (or computer,transform, manipulate, aggregate, summarize, etc.) the data beforesending the data from the vehicle, for example providing the appropriategranularity (e.g., value resolution) and sampling rates (e.g., temporalresolution) for each individual application. For example, the OBU may,for example, process the data in any manner deemed advantageous by thesystem. The OBU may, for example, send the collected data (e.g., rawdata, preprocessed data, information of metrics calculated based on thecollected data, etc.) to the Cloud (e.g., to one or more networkedservers coupled to any portion of the network) in an efficient andreliable manner to improve the efficiency, environmental impact andsocial value of municipal city operations and transportation services.Various example use cases are described herein.

In an example scenario in which public buses are moving along cityroutes and/or taxis are performing their private transportationservices, the OBU is able to collect large quantities of real-time datafrom the positioning systems (e.g., GPS, etc.), from accelerometermodules, etc. The OBU may then, for example, communicate such data tothe Cloud, where the data may be processed, reported and viewed, forexample to support such public or private bus and/or taxi operations,for example supporting efficient remote monitoring and scheduling ofbuses and taxis, respectively.

In an example implementation, small cameras (or other sensors) may becoupled to small single-board computers (SBCs) that are placed above thedoors of public buses to allow capturing image sequences of peopleentering and leaving buses, and/or on stops along the bus routes inorder to estimate the number of people waiting for a bus. Such data maybe gathered by the OBU in order to be sent to the Cloud. With such data,public transportation systems may detect peaks; overcrowded buses,routes and stops; underutilized buses, routes and stops; etc., enablingaction to be taken in real-time (e.g., reducing bus periodicity todecrease fuel costs and CO₂ emissions where and when passenger flows aresmaller, etc.) as well as detecting systematic transportation problems.

An OBU may, for example, be operable to communicate with any of avariety of Wi-Fi-enabled sensor devices equipped with a heterogeneouscollection of environmental sensors. Such sensors may, for example,comprise noise sensors (microphones, etc.), gas sensors (e.g., sensingCO, NO₂, O₃, volatile organic compounds (or VOCs), CO₂, etc.), smokesensors, pollution sensors, meteorological sensors (e.g., sensingtemperature, humidity, luminosity, particles, solar radiation, windspeed (e.g., anemometer), wind direction, rain (e.g., a pluviometer),optical scanners, biometric scanners, cameras, microphones, etc.). Suchsensors may also comprise sensors associated with users (e.g., vehicleoperators or passengers, passersby, etc.) and/or their personal devices(e.g., smart phones or watches, biometrics sensors, wearable sensors,implanted sensors, etc.). Such sensors may, for example, comprisesensors and/or systems associated with on-board diagnostic (OBD) unitsfor vehicles, autonomous vehicle driving systems, etc. Such sensors may,for example, comprise positioning sensors (e.g., GPS sensors, Galileosensors, GLONASS sensors, etc.). Note that such positioning sensors maybe part of a vehicle's operational system (e.g., a localhuman-controlled vehicle, an autonomous vehicle, a remotehuman-controlled vehicle, etc.) Such sensors may, for example, comprisecontainer sensors (e.g., garbage can sensors, shipping containersensors, container environmental sensors, container tracking sensors,etc.).

Once a vehicle enters the vicinity of such a sensor device, a wirelesslink may be established, so that the vehicle (or OBU thereof) cancollect sensor data from the sensor device and upload the collected datato a database in the Cloud. The appropriate action can then be taken. Inan example waste management implementation, several waste management (orcollection) trucks may be equipped with OBUs that are able toperiodically communicate with sensors installed on containers in orderto gather information about waste level, time passed since lastcollection, etc. Such information may then sent to the Cloud (e.g., to awaste management application coupled to the Internet, etc.) through thevehicular mesh network, in order to improve the scheduling and/orrouting of waste management trucks. Note that various sensors may alwaysbe in range of the Mobile AP (e.g., vehicle-mounted sensors). Note thatthe sensor may also (or alternatively) be mobile (e.g., a sensor mountedto another vehicle passing by a Mobile AP or Fixed AP, a drone-mountedsensor, a pedestrian-mounted sensor, etc.).

In an example implementation, for example in a controlled space (e.g., aport, harbor, airport, factory, plantation, mine, etc.) with manyvehicles, machines and employees, a communication network in accordancewith various aspects of the present disclosure may expand the wirelesscoverage of enterprise and/or local Wi-Fi networks, for example withoutresorting to a Telco-dependent solution based on SIM cards or cellularfees. In such an example scenario, apart from avoiding expensivecellular data plans, limited data rate and poor cellular coverage insome places, a communication network in accordance with various aspectsof the present disclosure is also able to collect and/or communicatelarge amounts of data, in a reliable and real-time manner, where suchdata may be used to optimize harbor logistics, transportationoperations, etc.

For example in a port and/or harbor implementation, by gatheringreal-time information on the position, speed, fuel consumption and CO₂emissions of the vehicles, the communication network allows a portoperator to improve the coordination of the ship loading processes andincrease the throughput of the harbor. Also for example, thecommunication network enables remote monitoring of drivers' behaviors,behaviors of autonomous vehicles and/or control systems thereof, trucks'positions and engines' status, and then be able to provide real-timenotifications to drivers (e.g., to turn on/off the engine, follow theright route inside the harbor, take a break, etc.), for example humandrivers and/or automated vehicle driving systems, thus reducing thenumber and duration of the harbor services and trips. Harbor authoritiesmay, for example, quickly detect malfunctioning trucks and abnormaltrucks' circulation, thus avoiding accidents in order to increase harborefficiency, security, and safety. Additionally, the vehicles can alsoconnect to Wi-Fi access points from harbor local operators, and provideWi-Fi Internet access to vehicles' occupants and surrounding harboremployees, for example allowing pilots to save time by filing reportsvia the Internet while still on the water.

FIG. 1 shows a block diagram of a communication network 100, inaccordance with various aspects of this disclosure. Any or all of thefunctionality discussed herein may be performed by any or all of theexample components of the example network 100. Also, the example network100 may, for example, share any or all characteristics with the otherexample networks and/or network components 200, 300, 400, 500-570, 600,700, 800, 900, 1000, 1100, and 1200, discussed herein.

The example network 100, for example, comprises a Cloud that may, forexample comprise any of a variety of network level components. The Cloudmay, for example, comprise any of a variety of server systems executingapplications that monitor and/or control components of the network 100.Such applications may also, for example, manage the collection ofinformation from any of a large array of networked information sources,many examples of which are discussed herein. The Cloud (or a portionthereof) may also be referred to, at times, as an API. For example,Cloud (or a portion thereof) may provide one or more applicationprogramming interfaces (APIs) which other devices may use forcommunicating/interacting with the Cloud.

An example component of the Cloud may, for example, manageinteroperability with various multi-Cloud systems and architectures.Another example component (e.g., a Cloud service component) may, forexample, provide various Cloud services (e.g., captive portal services,authentication, authorization, and accounting (AAA) services, APIGateway services, etc.). An additional example component (e.g., aDevCenter component) may, for example, provide network monitoring and/ormanagement functionality, manage the implementation of software updates,etc. A further example component of the Cloud may manage data storage,data analytics, data access, etc. A still further example component ofthe Cloud may include any of a variety of third-partly applications andservices.

The Cloud may, for example, be coupled to the Backbone/CoreInfrastructure of the example network 100 via the Internet (e.g.,utilizing one or more Internet Service Providers). Though the Internetis provided by example, it should be understood that scope of thepresent disclosure is not limited thereto.

The Backbone/Core may, for example, comprise any one or more differentcommunication infrastructure components. For example, one or moreproviders may provide backbone networks or various components thereof.As shown in the example network 100 illustrated in FIG. 1, a Backboneprovider may provide wireline access (e.g., PSTN, fiber, cable, etc.).Also for example, a Backbone provider may provide wireless access (e.g.,Microwave, LTE/Cellular, 5G/TV Spectrum, etc.).

The Backbone/Core may also, for example, comprise one or more LocalInfrastructure Providers. The Backbone/Core may also, for example,comprise a private infrastructure (e.g., run by the network 100implementer, owner, etc.). The Backbone/Core may, for example, provideany of a variety of Backbone Services (e.g., AAA, Mobility, Monitoring,Addressing, Routing, Content services, Gateway Control services, etc.).

The Backbone/Core Infrastructure may comprise any of a variety ofcharacteristics, non-limiting examples of which are provided herein. Forexample, the Backbone/Core may be compatible with different wireless orwired technologies for backbone access. The Backbone/Core may also beadaptable to handle public (e.g., municipal, city, campus, etc.) and/orprivate (e.g., ports, campus, etc.) network infrastructures owned bydifferent local providers, and/or owned by the network implementer orstakeholder. The Backbone/Core may, for example, comprise and/orinterface with different Authentication, Authorization, and Accounting(AAA) mechanisms.

The Backbone/Core Infrastructure may, for example, support differentmodes of operation (e.g., L2 in port implementations, L3 in on-landpublic transportation implementations, utilizing any one or more of aplurality of different layers of digital IP networking, any combinationsthereof, equivalents thereof, etc.) or addressing pools. TheBackbone/Core may also for example, be agnostic to the Cloud provider(s)and/or Internet Service Provider(s). Additionally for example, theBackbone/Core may be agnostic to requests coming from any or allsubsystems of the network 100 (e.g., Mobile APs or OBUs (On BoardUnits), Fixed APs or RSUs (Road Side Units), MCs (Mobility Controllers)or LMAs (Local Mobility Anchors) or Network Controllers, etc.) and/orthird-party systems.

The Backbone/Core Infrastructure may, for example, comprise the abilityto utilize and/or interface with different data storage / processingsystems (e.g., MongoDB, MySql, Redis, etc.). The Backbone/CoreInfrastructure may further, for example, provide different levels ofsimultaneous access to the infrastructure, services, data, etc.

The example network 100 may also, for example, comprise a Fixed HotspotAccess Network. Various example characteristics of such a Fixed HotspotAccess Network 200 are shown at FIG. 2. The example network 200 may, forexample, share any or all characteristics with the other examplenetworks and/or network components 100, 300, 400, 500-570, 600, 700,800, 900, 1000, 1100, and 1200 discussed herein.

In the example network 200, the Fixed APs (e.g., the proprietary APs,the public third party APs, the private third party APs, etc.) may bedirectly connected to the local infrastructure provider and/or to thewireline/wireless backbone. Also for example, the example network 200may comprise a mesh between the various APs via wireless technologies.Note, however, that various wired technologies may also be utilizeddepending on the implementation. As shown, different fixed hotspotaccess networks can be connected to a same backbone provider, but mayalso be connected to different respective backbone providers. In anexample implementation utilizing wireless technology for backboneaccess, such an implementation may be relatively fault tolerant. Forexample, a Fixed AP may utilize wireless communications to the backbonenetwork (e.g., cellular, 3G, LTE, other wide or metropolitan areanetworks, etc.) if the backhaul infrastructure is down. Also forexample, such an implementation may provide for relatively easyinstallation (e.g., a Fixed AP with no cable power source that can beplaced virtually anywhere).

In the example network 200, the same Fixed AP can simultaneously provideaccess to multiple Fixed APs, Mobile APs (e.g., vehicle OBUs, etc.),devices, user devices, sensors, things, etc. For example, a plurality ofmobile hotspot access networks (e.g., OBU-based networks, etc.) mayutilize the same Fixed AP. Also for example, the same Fixed AP canprovide a plurality of simultaneous accesses to another single unit(e.g., another Fixed AP, Mobile AP, device, etc.), for example utilizingdifferent channels, different radios, etc.).

Note that a plurality of Fixed APs may be utilized forfault-tolerance/fail-recovery purposes. In an example implementation, aFixed AP and its fail-over AP may both be normally operational (e.g., ina same switch). Also for example, one or more Fixed APs may be placed inthe network at various locations in an inactive or monitoring mode, andready to become operational when needed (e.g., in response to a fault,in response to an emergency services need, in response to a data surge,etc.).

Referring back to FIG. 1, the example Fixed Hotspot Access Network isshown with a wireless communication link to a backbone provider (e.g.,to one or more Backbone Providers and/or Local InfrastructureProviders), to a Mobile Hotspot Access Network, to one or more End UserDevices, and to the Environment. Also, the example Fixed Hotspot AccessNetwork is shown with a wired communication link to one or more BackboneProviders, to the Mobile Hotspot Access Network, to one or more End UserDevices, and to the Environment. The Environment may comprise any of avariety of devices (e.g., in-vehicle networks, devices, and sensors;autonomous vehicle networks, devices, and sensors; maritime (orwatercraft) and port networks, devices, and sensors; generalcontrolled-space networks, devices, and sensors; residential networks,devices, and sensors; disaster recovery & emergency networks, devices,and sensors; military and aircraft networks, devices, and sensors; smartcity networks, devices, and sensors; event (or venue) networks, devices,and sensors; underwater and underground networks, devices, and sensors;agricultural networks, devices, and sensors; tunnel (auto, subway,train, etc.) networks, devices, and sensors; parking networks, devices,and sensors; security and surveillance networks, devices, and sensors;shipping equipment and container networks, devices, and sensors;environmental control or monitoring networks, devices, and sensors;municipal networks, devices, and sensors; waste management networks,devices, and sensors, road maintenance networks, devices, and sensors,traffic management networks, devices, and sensors; advertising networks,devices and sensors; etc.).

The example network 100 of FIG. 1 also comprises a Mobile Hotspot AccessNetwork. Various example characteristics of such a Mobile Hotspot AccessNetwork 300 are shown at FIG. 3. Note that various fixed networkcomponents (e.g., Fixed APs) are also illustrated. The example network300 may, for example, share any or all characteristics with the otherexample networks and/or network components 100, 200, 400, 500-570, 600,700, 800, 900, 1000, 1100, and 1200 discussed herein.

The example network 300 comprises a wide variety of Mobile APs (orhotspots) that provide access to user devices, provide for sensor datacollection, provide multi-hop connectivity to other Mobile APs, etc. Forexample, the example network 300 comprises vehicles from differentfleets (e.g., aerial, terrestrial, underground, (under)water, etc.). Forexample, the example network 300 comprises one or more massdistribution/transportation fleets, one or more mass passengertransportation fleets, private/public shared-user fleets, privatevehicles, urban and municipal fleets, maintenance fleets, drones,watercraft (e.g., boats, ships, speedboats, tugboats, barges, etc.),emergency fleets (e.g., police, ambulance, firefighter, etc.), etc.

The example network 300, for example, shows vehicles from differentfleets directly connected and/or mesh connected, for example using sameor different communication technologies. The example network 300 alsoshows fleets simultaneously connected to different Fixed APs, which mayor may not belong to different respective local infrastructureproviders. As a fault-tolerance mechanism, the example network 300 mayfor example comprise the utilization of long-range wirelesscommunication network (e.g., cellular, 3G, 4G, LTE, etc.) in vehicles ifthe local network infrastructure is down or otherwise unavailable. Asame vehicle (e.g., Mobile AP or OBU) can simultaneously provide accessto multiple vehicles, devices, things, etc., for example using a samecommunication technology (e.g., shared channels and/or differentrespective channels thereof) and/or using a different respectivecommunication technology for each. Also for example, a same vehicle canprovide multiple accesses to another vehicle, device, thing, etc., forexample using a same communication technology (e.g., shared channelsand/or different respective channels thereof, and/or using a differentcommunication technology).

Additionally, multiple network elements may be connected together toprovide for fault-tolerance or fail recovery, increased throughput, orto achieve any or a variety of a client's networking needs, many ofexamples of which are provided herein. For example, two Mobile APs (orOBUs) may be installed in a same vehicle, etc.

Referring back to FIG. 1, the example Mobile Hotspot Access Network isshown with a wireless communication link to a backbone provider (e.g.,to one or more Backbone Providers and/or Local InfrastructureProviders), to a Fixed Hotspot Access Network, to one or more End UserDevice, and to the Environment (e.g., to any one of more of the sensorsor systems discussed herein, any other device or machine, etc.). Thoughthe Mobile Hotspot Access Network is not shown having a wired link tothe various other components, there may (at least at times) be such awired link, at least temporarily.

The example network 100 of FIG. 1 also comprises a set of End-UserDevices. Various example end user devices are shown at FIG. 4. Note thatvarious other network components (e.g., Fixed Hotspot Access Networks,Mobile Hotspot Access Network(s), the Backbone/Core, etc.) are alsoillustrated. The example network 400 may, for example, share any or allcharacteristics with the other example networks and/or networkcomponents 100, 200, 300, 500-570, 600, 700, 800, 900, 1000, 1100, and1200 discussed herein.

The example network 400 shows various mobile networked devices. Suchnetwork devices may comprise end-user devices (e.g., smartphones,tablets, smartwatches, laptop computers, webcams, personal gamingdevices, personal navigation devices, personal media devices, personalcameras, health-monitoring devices, personal location devices,monitoring panels, printers, etc.). Such networked devices may alsocomprise any of a variety of devices operating in the generalenvironment, where such devices might not for example be associated witha particular user (e.g. any or all of the sensor devices discussedherein, vehicle sensors, municipal sensors, fleet sensors road sensors,environmental sensors, security sensors, traffic sensors, waste sensors,meteorological sensors, any of a variety of different types of municipalor enterprise equipment, etc.). Any of such networked devices can beflexibly connected to distinct backbone, fixed hotspot access networks,mobile hotspot access networks, etc., using the same or differentwired/wireless technologies.

A mobile device may, for example, operate as an AP to providesimultaneous access to multiple devices/things, which may then form adhoc networks, interconnecting devices ultimately connected to distinctbackbone networks, fixed hotspot, and/or mobile hotspot access networks.Devices (e.g., any or all of the devices or network nodes discussedherein) may, for example, have redundant technologies to access distinctbackbone, fixed hotspot, and/or mobile hotspot access networks, forexample for fault-tolerance and/or load-balancing purposes (e.g.,utilizing multiple SIM cards, etc.). A device may also, for example,simultaneously access distinct backbone, fixed hotspot access networks,and/or mobile hotspot access networks, belonging to the same provider orto different respective providers. Additionally for example, a devicecan provide multiple accesses to another device/thing (e.g., viadifferent channels, radios, etc.).

Referring back to FIG. 1, the example End-User Devices are shown with awireless communication link to a backbone provider (e.g., to one or moreBackbone Providers and/or Local Infrastructure Providers), to a FixedHotspot Access Network, to a Mobile Hotspot Access Network, and to theEnvironment. Also for example, the example End-User Devices are shownwith a wired communication link to a backbone provider, to a FixedHotspot Access Network, to a Mobile Hotspot Access Network, and to theEnvironment.

The example network 100 illustrated in FIG. 1 has a flexiblearchitecture that is adaptable at implementation time (e.g., fordifferent use cases) and/or adaptable in real-time, for example asnetwork components enter and leave service. FIGS. 5A-5C illustrate suchflexibility by providing example modes (or configurations). The examplenetworks 500-570 may, for example, share any or all characteristics withthe other example networks and/or network components 100, 200, 300, 400,500-570, 600, 700, 800, 900, 1000, 1100, and 1200 discussed herein. Forexample and without limitation, any or all of the communication links(e.g., wired links, wireless links, etc.) shown in the example networks500-570 are generally analogous to similarly positioned communicationlinks shown in the example network 100 of FIG. 1.

For example, various aspects of this disclosure provide communicationnetwork architectures, systems, and methods for supporting a dynamicallyconfigurable communication network comprising a complex array of bothstatic and moving communication nodes (e.g., the Internet of movingthings). For example, a communication network implemented in accordancewith various aspects of the present disclosure may operate in one of aplurality of modalities comprising various fixed nodes, mobile nodes,and/or a combination thereof, which are selectable to yield any of avariety of system goals (e.g., increased throughput, reduced latency andpacket loss, increased availability and robustness of the system, extraredundancy, increased responsiveness, increased security in thetransmission of data and/or control packets, reduced number ofconfiguration changes by incorporating smart thresholds (e.g., change oftechnology, change of certificate, change of IP, etc.), providingconnectivity in dead zones or zones with difficult access, reducing thecosts for maintenance and accessing the equipment forupdating/upgrading, etc.). At least some of such modalities may, forexample, be entirely comprised of fixed-position nodes, at leasttemporarily if not permanently.

For illustrative simplicity, many of the example aspects shown in theexample system or network 100 of FIG. 1 (and other Figures herein) areomitted from FIGS. 5A-5C, but may be present. For example, the Cloud,Internet, and ISP aspects shown in FIG. 1 and in other Figures are notexplicitly shown in FIGS. 5A-5C, but may be present in any of theexample configurations (e.g., as part of the backbone provider networkor coupled thereto, as part of the local infrastructure provider networkor coupled thereto, etc.).

For example, the first example mode 500 is presented as a normalexecution mode, for example a mode (or configuration) in which all ofthe components discussed herein are present. For example, thecommunication system in the first example mode 500 comprises a backboneprovider network, a local infrastructure provider network, a fixedhotspot access network, a mobile hotspot access network, end-userdevices, and environment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the first example mode 500 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via a wired link. Note that such a wiredcoupling may be temporary. Also note that in various exampleconfigurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5A, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the first example mode 500 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links. Also note that in various example configurations,the backbone provider network may also be communicatively coupled to thelocal infrastructure provider network via one or more wireless (ornon-tethered) links.

Though not shown in the first example mode 500 (or any of the examplemodes of FIGS. 5A-5C), one or more servers may be communicativelycoupled to the backbone provider network and/or the local infrastructurenetwork. FIG. 1 provides an example of Cloud servers beingcommunicatively coupled to the backbone provider network via theInternet.

As additionally shown in FIG. 5A, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the first example mode 500(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), fixed hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wired links. Note that such a wired coupling may be temporary. Alsonote that in various example configurations, the local infrastructureprovider network may also, at least temporarily, be communicativelycoupled to the mobile hotspot access network (or any component thereof)via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the first example mode 500 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the fixed hotspot access network (or any componentthereof), the mobile hotspot access network (or any component thereof),the end-user devices, and/or environment devices via one or morewireless links. Note that the communication link shown in the firstexample mode 500 of FIG. 5A between the local infrastructure providernetwork and the fixed hotspot access network may be wired and/orwireless.

The fixed hotspot access network is also shown in the first example mode500 to be communicatively coupled to the mobile hotspot access network,the end-user devices, and/or environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein. Additionally, the mobile hotspot access network is further shownin the first example mode 500 to be communicatively coupled to theend-user devices and/or environment devices via one or more wirelesslinks. Many examples of such wireless coupling are provided herein.Further, the end-user devices are also shown in the first example mode500 to be communicatively coupled to the environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Note that in various example implementations any ofsuch wireless links may instead (or in addition) comprise a wired (ortethered) link.

In the first example mode 500 (e.g., the normal mode), information (ordata) may be communicated between an end-user device and a server (e.g.,a computer system) via the mobile hotspot access network, the fixedhotspot access network, the local infrastructure provider network,and/or the backbone provider network. As will be seen in the variousexample modes presented herein, such communication may flexibly occurbetween an end-user device and a server via any of a variety ofdifferent communication pathways, for example depending on theavailability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the fixed hotspot access network, thelocal infrastructure provider network, and/or the backbone providernetwork (e.g., skipping the mobile hotspot access network). Also forexample, information communicated between an end user device and aserver may be communicated via the backbone provider network (e.g.,skipping the mobile hotspot access network, fixed hotspot accessnetwork, and/or local infrastructure provider network).

Similarly, in the first example mode 500 (e.g., the normal mode),information (or data) may be communicated between an environment deviceand a server via the mobile hotspot access network, the fixed hotspotaccess network, the local infrastructure provider network, and/or thebackbone provider network. Also for example, an environment device maycommunicate with or through an end-user device (e.g., instead of or inaddition to the mobile hotspot access network). As will be seen in thevarious example modes presented herein, such communication may flexiblyoccur between an environment device and a server (e.g., communicativelycoupled to the local infrastructure provider network and/or backboneprovider network) via any of a variety of different communicationpathways, for example depending on the availability of a network,depending on bandwidth utilization goals, depending on communicationpriority, depending on communication time (or latency) and/orreliability constraints, depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the fixed hotspot access network, thelocal infrastructure provider network, and/or the backbone providernetwork (e.g., skipping the mobile hotspot access network). Also forexample, information communicated between an environment device and aserver may be communicated via the backbone provider network (e.g.,skipping the mobile hotspot access network, fixed hotspot accessnetwork, and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the mobile hotspot access network and/or fixed hotspotaccess network).

As discussed herein, the example networks presented herein areadaptively configurable to operate in any of a variety of differentmodes (or configurations). Such adaptive configuration may occur atinitial installation and/or during subsequent controlled networkevolution (e.g., adding or removing any or all of the network componentsdiscussed herein, expanding or removing network capacity, adding orremoving coverage areas, adding or removing services, etc.). Suchadaptive configuration may also occur in real-time, for example inresponse to real-time changes in network conditions (e.g., networks orcomponents thereof being available or not based on vehicle oruser-device movement, network or component failure, network or componentreplacement or augmentation activity, network overloading, etc.). Thefollowing example modes are presented to illustrate characteristics ofvarious modes in which a communication system may operate in accordancewith various aspects of the present disclosure. The following examplemodes will generally be discussed in relation to the first example mode500 (e.g., the normal execution mode). Note that such example modes aremerely illustrative and not limiting.

The second example mode (or configuration) 510 (e.g., a no backboneavailable mode) may, for example, share any or all characteristics withthe first example mode 500, albeit without the backbone provider networkand communication links therewith. For example, the communication systemin the second example mode 510 comprises a local infrastructure providernetwork, a fixed hotspot access network, a mobile hotspot accessnetwork, end-user devices, and environment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the localinfrastructure provider network may be communicatively coupled to any orall of the other elements present in the second example mode 510 (orconfiguration) via one or more wired (or tethered) links. For example,the local infrastructure provider network may be communicatively coupledto the fixed hotspot access network (or any component thereof), theend-user devices, and/or environment devices via one or more wiredlinks. Note that such a wired coupling may be temporary. Also note thatin various example configurations, the local infrastructure providernetwork may also, at least temporarily, be communicatively coupled tothe mobile hotspot access network (or any component thereof) via one ormore wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the second example mode 510 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links. Note that the communication link(s) shown in thesecond example mode 510 of FIG. 5A between the local infrastructureprovider network and the fixed hotspot access network may be wiredand/or wireless.

The fixed hotspot access network is also shown in the second examplemode 510 to be communicatively coupled to the mobile hotspot accessnetwork, the end-user devices, and/or environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Additionally, the mobile hotspot access network isfurther shown in the second example mode 510 to be communicativelycoupled to the end-user devices and/or environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Further, the end-user devices are also shown in thesecond example mode 510 to be communicatively coupled to the environmentdevices via one or more wireless links. Many examples of such wirelesscoupling are provided herein. Note that in various exampleimplementations any of such wireless links may instead (or in addition)comprise a wired (or tethered) link.

In the second example mode 510 (e.g., the no backbone available mode),information (or data) may be communicated between an end-user device anda server (e.g., a computer, etc.) via the mobile hotspot access network,the fixed hotspot access network, and/or the local infrastructureprovider network. As will be seen in the various example modes presentedherein, such communication may flexibly occur between an end-user deviceand a server via any of a variety of different communication pathways,for example depending on the availability of a network, depending onbandwidth utilization goals, depending on communication priority,depending on communication time (or latency) and/or reliabilityconstraints, depending on cost, etc. For example, informationcommunicated between an end user device and a server may be communicatedvia the fixed hotspot access network and/or the local infrastructureprovider network (e.g., skipping the mobile hotspot access network).Also for example, information communicated between an end user deviceand a server may be communicated via the local infrastructure providernetwork (e.g., skipping the mobile hotspot access network and/or fixedhotspot access network).

Similarly, in the second example mode 510 (e.g., the no backboneavailable mode), information (or data) may be communicated between anenvironment device and a server via the mobile hotspot access network,the fixed hotspot access network, and/or the local infrastructureprovider network. Also for example, an environment device maycommunicate with or through an end-user device (e.g., instead of or inaddition to the mobile hotspot access network). As will be seen in thevarious example modes presented herein, such communication may flexiblyoccur between an environment device and a server (e.g., communicativelycoupled to the local infrastructure provider network) via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the fixed hotspot access network and/orthe local infrastructure provider network (e.g., skipping the mobilehotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thelocal infrastructure provider network (e.g., skipping the mobile hotspotaccess network and/or fixed hotspot access network).

The second example mode 510 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. Forexample, due to security and/or privacy goals, the second example mode510 may be utilized so that communication access to the public Cloudsystems, the Internet in general, etc., is not allowed. For example, allnetwork control and management functions may be within the localinfrastructure provider network (e.g., wired local network, etc.) and/orthe fixed access point network.

In an example implementation, the communication system might be totallyowned, operated and/or controlled by a local port authority. No extraexpenses associated with cellular connections need be spent. Forexample, cellular connection capability (e.g., in Mobile APs, Fixed APs,end user devices, environment devices, etc.) need not be provided. Notealso that the second example mode 510 may be utilized in a scenario inwhich the backbone provider network is normally available but iscurrently unavailable (e.g., due to server failure, due to communicationlink failure, due to power outage, due to a temporary denial of service,etc.).

The third example mode (or configuration) 520 (e.g., a no localinfrastructure and fixed hotspots available mode) may, for example,share any or all characteristics with the first example mode 500, albeitwithout the local infrastructure provider network, the fixed hotspotaccess network, and communication links therewith. For example, thecommunication system in the third example mode 520 comprises a backboneprovider network, a mobile hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the third example mode 520 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the end-user devicesand/or environment devices via one or more wired links. Note that such awired coupling may be temporary. Also note that in various exampleconfigurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5A, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the third example mode 520 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links.

The mobile hotspot access network is further shown in the third examplemode 520 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the third example mode 520 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein. Note that in various example implementations any of suchwireless links may instead (or in addition) comprise a wired (ortethered) link.

In the third example mode 520 (e.g., the no local infrastructure andfixed hotspots available mode), information (or data) may becommunicated between an end-user device and a server (e.g., a computer,etc.) via the mobile hotspot access network and/or the backbone providernetwork. As will be seen in the various example modes presented herein,such communication may flexibly occur between an end-user device and aserver via any of a variety of different communication pathways, forexample depending on the availability of a network, depending onbandwidth utilization goals, depending on communication priority,depending on communication time (or latency) and/or reliabilityconstraints, depending on cost, etc. For example, informationcommunicated between an end user device and a server may be communicatedvia the backbone provider network (e.g., skipping the mobile hotspotaccess network).

Similarly, in the third example mode 520 (e.g., the no localinfrastructure and fixed hotspots available mode), information (or data)may be communicated between an environment device and a server via themobile hotspot access network and/or the backbone provider network. Alsofor example, an environment device may communicate with or through anend-user device (e.g., instead of or in addition to the mobile hotspotaccess network). As will be seen in the various example modes presentedherein, such communication may flexibly occur between an environmentdevice and a server (e.g., communicatively coupled to the backboneprovider network) via any of a variety of different communicationpathways, for example depending on the availability of a network,depending on bandwidth utilization goals, depending on communicationpriority, depending on communication time (or latency) and/orreliability constraints, depending on cost, etc. For example,information communicated between an environment device and a server maybe communicated via the backbone provider network (e.g., skipping themobile hotspot access network).

In the third example mode 520, all control/management functions may forexample be implemented within the Cloud. For example, since the mobilehotspot access network does not have a communication link via a fixedhotspot access network, the Mobile APs may utilize a direct connection(e.g., a cellular connection) with the backbone provider network (orCloud). If a Mobile AP does not have such capability, the Mobile AP mayalso, for example, utilize data access provided by the end-user devicescommunicatively coupled thereto (e.g., leveraging the data plans of theend-user devices).

The third example mode 520 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the third example mode 520 may be utilized in anearly stage of a larger deployment, for example deployment that willgrow into another mode (e.g., the example first mode 500, example fourthmode 530, etc.) as more communication system equipment is installed.Note also that the third example mode 520 may be utilized in a scenarioin which the local infrastructure provider network and fixed hotspotaccess network are normally available but are currently unavailable(e.g., due to equipment failure, due to communication link failure, dueto power outage, due to a temporary denial of service, etc.).

The fourth example mode (or configuration) 530 (e.g., a no fixedhotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without thefixed hotspot access network and communication links therewith. Forexample, the communication system in the fourth example mode 530comprises a backbone provider network, a local infrastructure providernetwork, a mobile hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the fourth example mode 530 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), the end-userdevices, and/or environment devices via one or more wired links. Notethat such a wired coupling may be temporary. Also note that in variousexample configurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the fourth example mode 530 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Also note that in various exampleconfigurations, the backbone provider network may also becommunicatively coupled to the local infrastructure provider network viaone or more wireless (or non-tethered) links.

As additionally shown in FIG. 5B, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the fourth example mode 530(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wired links. Note that such a wired coupling may betemporary. Also note that in various example configurations, the localinfrastructure provider network may also, at least temporarily, becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof) via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the fourth example mode 530 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links.

The mobile hotspot access network is further shown in the fourth examplemode 530 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the fourth example mode 530 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the fourth example mode 530 (e.g., the no fixed hotspots mode),information (or data) may be communicated between an end-user device anda server via the mobile hotspot access network, the local infrastructureprovider network, and/or the backbone provider network. As will be seenin the various example modes presented herein, such communication mayflexibly occur between an end-user device and a server via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the local infrastructure provider networkand/or the backbone provider network (e.g., skipping the mobile hotspotaccess network). Also for example, information communicated between anend user device and a server may be communicated via the backboneprovider network (e.g., skipping the mobile hotspot access networkand/or local infrastructure provider network).

Similarly, in the fourth example mode 530 (e.g., the no fixed hotspotsavailable mode), information (or data) may be communicated between anenvironment device and a server via the mobile hotspot access network,the local infrastructure provider network, and/or the backbone providernetwork. Also for example, an environment device may communicate with orthrough an end-user device (e.g., instead of or in addition to themobile hotspot access network). As will be seen in the various examplemodes presented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network and/or backbone provider network)via any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the local infrastructure providernetwork and/or the backbone provider network (e.g., skipping the mobilehotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thebackbone provider network (e.g., skipping the mobile hotspot accessnetwork and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the mobile hotspot access network and/or backboneprovider network).

In the fourth example mode 530, in an example implementation, some ofthe control/management functions may for example be implemented withinthe local backbone provider network (e.g., within a client premises).For example, communication to the local infrastructure provider may beperformed through the backbone provider network (or Cloud). Note that ina scenario in which there is a direct communication pathway between thelocal infrastructure provider network and the mobile hotspot accessnetwork, such communication pathway may be utilized.

For example, since the mobile hotspot access network does not have acommunication link via a fixed hotspot access network, the Mobile APsmay utilize a direct connection (e.g., a cellular connection) with thebackbone provider network (or Cloud). If a Mobile AP does not have suchcapability, the Mobile AP may also, for example, utilize data accessprovided by the end-user devices communicatively coupled thereto (e.g.,leveraging the data plans of the end-user devices).

The fourth example mode 530 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the fourth example mode 530 may be utilized inan early stage of a larger deployment, for example a deployment thatwill grow into another mode (e.g., the example first mode 500, etc.) asmore communication system equipment is installed. The fourth examplemode 530 may, for example, be utilized in a scenario in which there isno fiber (or other) connection available for Fixed APs (e.g., in amaritime scenario, in a plantation scenario, etc.), or in which a FixedAP is difficult to access or connect. For example, one or more MobileAPs of the mobile hotspot access network may be used as gateways toreach the Cloud. The fourth example mode 530 may also, for example, beutilized when a vehicle fleet and/or the Mobile APs associated therewithare owned by a first entity and the Fixed APs are owned by anotherentity, and there is no present agreement for communication between theMobile APs and the Fixed APs. Note also that the fourth example mode 530may be utilized in a scenario in which the fixed hotspot access networkis normally available but are currently unavailable (e.g., due toequipment failure, due to communication link failure, due to poweroutage, due to a temporary denial of service, etc.).

The fifth example mode (or configuration) 540 (e.g., a no mobilehotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without themobile hotspot access network and communication links therewith. Forexample, the communication system in the fifth example mode 540comprises a backbone provider network, a local infrastructure providernetwork, a fixed hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the fifth example mode 540 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via one or more wired links. Note that such awired coupling may be temporary.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the fifth example mode 540 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Also note that in various exampleconfigurations, the backbone provider network may also becommunicatively coupled to the local infrastructure provider network viaone or more wireless (or non-tethered) links.

As additionally shown in FIG. 5B, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the fifth example mode 540(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), fixed hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wired links. Note that such a wired coupling may be temporary. Alsonote that in various example configurations, the local infrastructureprovider network may also, at least temporarily, be communicativelycoupled to the mobile hotspot access network (or any component thereof)via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the fifth example mode 540 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network, the fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via one or more wireless links. Note that thecommunication link(s) shown in the fifth example mode 540 of FIG. 5Bbetween the local infrastructure provider network and the fixed hotspotaccess network may be wired and/or wireless.

The fixed hotspot access network is also shown in the fifth example mode540 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the fifth example mode 540 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the fifth example mode 540 (e.g., the no mobile hotspots availablemode), information (or data) may be communicated between an end-userdevice and a server via the fixed hotspot access network, the localinfrastructure provider network, and/or the backbone provider network.As will be seen in the various example modes presented herein, suchcommunication may flexibly occur between an end-user device and a servervia any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc. For example, information communicated between anend user device and a server may be communicated via the localinfrastructure provider network, and/or the backbone provider network(e.g., skipping the fixed hotspot access network). Also for example,information communicated between an end user device and a server may becommunicated via the backbone provider network (e.g., skipping the fixedhotspot access network and/or local infrastructure provider network).

Similarly, in the fifth example mode 540 (e.g., the no mobile hotspotsavailable mode), information (or data) may be communicated between anenvironment device and a server via the fixed hotspot access network,the local infrastructure provider network, and/or the backbone providernetwork. Also for example, an environment device may communicate with orthrough an end-user device (e.g., instead of or in addition to the fixedhotspot access network). As will be seen in the various example modespresented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network and/or backbone provider network)via any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the local infrastructure providernetwork and/or the backbone provider network (e.g., skipping the fixedhotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thebackbone provider network (e.g., skipping the fixed hotspot accessnetwork and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the fixed hotspot access network and/or the backboneprovider network).

In the fifth example mode 540, in an example implementation, theend-user devices and environment devices may communicate directly toFixed APs (e.g., utilizing Ethernet, Wi-Fi, etc.). Also for example, theend-user devices and/or environment devices may communicate directlywith the backbone provider network (e.g., utilizing cellularconnections, etc.).

The fifth example mode 540 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation in which end-user devices and/or environmentdevices may communicate directly with Fixed APs, such communication maybe utilized instead of Mobile AP communication. For example, the fixedhotspot access network might provide coverage for all desired areas.

Note also that the fifth example mode 540 may be utilized in a scenarioin which the fixed hotspot access network is normally available but iscurrently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

The sixth example mode (or configuration) 550 (e.g., the no fixed/mobilehotspots and local infrastructure available mode) may, for example,share any or all characteristics with the first example mode 500, albeitwithout the local infrastructure provider network, fixed hotspot accessnetwork, mobile hotspot access network, and communication linkstherewith. For example, the communication system in the sixth examplemode 550 comprises a backbone provider network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the sixth example mode 550 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the end-user devicesand/or environment devices via one or more wired links. Note that such awired coupling may be temporary.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the sixth example mode 550 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the end-user devices and/or environmentdevices via one or more wireless links.

The end-user devices are also shown in the sixth example mode 550 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the sixth example mode 550 (e.g., the no fixed/mobile hotspots andlocal infrastructure available mode), information (or data) may becommunicated between an end-user device and a server via the backboneprovider network. Similarly, in the sixth example mode 550 (e.g., the nofixed/mobile hotspots and local infrastructure mode), information (ordata) may be communicated between an environment device and a server viathe backbone provider network. Also for example, an environment devicemay communicate with or through an end-user device (e.g., instead of orin addition to the mobile hotspot access network).

The sixth example mode 550 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, for example in which an end-user has not yetsubscribed to the communication system, the end-user device maysubscribe to the system through a Cloud application and by communicatingdirectly with the backbone provider network (e.g., via cellular link,etc.). The sixth example mode 550 may also, for example, be utilized inrural areas in which Mobile AP presence is sparse, Fixed AP installationis difficult or impractical, etc.

Note also that the sixth example mode 550 may be utilized in a scenarioin which the infrastructure provider network, fixed hotspot accessnetwork, and/or mobile hotspot access network are normally available butare currently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

The seventh example mode (or configuration) 560 (e.g., the no backboneand mobile hotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without thebackbone provider network, mobile hotspot access network, andcommunication links therewith. For example, the communication system inthe seventh example mode 560 comprises a local infrastructure providernetwork, fixed hotspot access network, end-user devices, and environmentdevices.

As shown in FIG. 5C, and in FIG. 1 in more detail, the localinfrastructure provider network may be communicatively coupled to any orall of the other elements present in the seventh example mode 560 (orconfiguration) via one or more wired (or tethered) links. For example,the local infrastructure provider network may be communicatively coupledto the fixed hotspot access network (or any component thereof), theend-user devices, and/or environment devices via one or more wiredlinks. Note that such a wired coupling may be temporary.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the seventh example mode 560 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Note that the communication link shown inthe seventh example mode 560 of FIG. 5C between the local infrastructureprovider network and the fixed hotspot access network may be wiredand/or wireless.

The fixed hotspot access network is also shown in the seventh examplemode 560 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Additionally, the end-userdevices are also shown in the seventh example mode 560 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the seventh example mode 560 (e.g., the no backbone and mobilehotspots available mode), information (or data) may be communicatedbetween an end-user device and a server via the fixed hotspot accessnetwork and/or the local infrastructure provider network. As will beseen in the various example modes presented herein, such communicationmay flexibly occur between an end-user device and a server via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the fixed hotspot access network).

Similarly, in the seventh example mode 560 (e.g., the no backbone andmobile hotspots available mode), information (or data) may becommunicated between an environment device and a server via the fixedhotspot access network and/or the local infrastructure provider network.Also for example, an environment device may communicate with or throughan end-user device (e.g., instead of or in addition to the mobilehotspot access network). As will be seen in the various example modespresented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network) via any of a variety of differentcommunication pathways, for example depending on the availability of anetwork, depending on bandwidth utilization goals, depending oncommunication priority, depending on communication time (or latency)and/or reliability constraints, depending on cost, etc. For example,information communicated between an environment device and a server maybe communicated via the local infrastructure provider network (e.g.,skipping the fixed hotspot access network).

The seventh example mode 560 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample controlled space implementation, Cloud access might not beprovided (e.g., for security reasons, privacy reasons, etc.), and full(or sufficient) coverage of the coverage area is provided by the fixedhotspot access network, and thus the mobile hotspot access network isnot needed. For example, the end-user devices and environment devicesmay communicate directly (e.g., via Ethernet, Wi-Fi, etc.) with theFixed APs

Note also that the seventh example mode 560 may be utilized in ascenario in which the backbone provider network and/or fixed hotspotaccess network are normally available but are currently unavailable(e.g., due to equipment failure, due to communication link failure, dueto power outage, due to a temporary denial of service, etc.).

The eighth example mode (or configuration) 570 (e.g., the no backbone,fixed hotspots, and local infrastructure available mode) may, forexample, share any or all characteristics with the first example mode500, albeit without the backbone provider network, local infrastructureprovider network, fixed hotspot access network, and communication linkstherewith. For example, the communication system in the eighth examplemode 570 comprises a mobile hotspot access network, end-user devices,and environment devices.

As shown in FIG. 5C, and in FIG. 1 in more detail, the mobile hotspotaccess network is shown in the eighth example mode 570 to becommunicatively coupled to the end-user devices and/or environmentdevices via one or more wireless links. Many examples of such wirelesscoupling are provided herein. Further, the end-user devices are alsoshown in the eighth example mode 570 to be communicatively coupled tothe environment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein.

In the eighth example mode 570 (e.g., the no backbone, fixed hotspots,and local infrastructure available mode), information (or data) mightnot (at least currently) be communicated between an end-user device anda server (e.g., a coupled to the backbone provider network, localinfrastructure provider network, etc.). Similarly, information (or data)might not (at least currently) be communicated between an environmentdevice and a server (e.g., a coupled to the backbone provider network,local infrastructure provider network, etc.). Note that the environmentdevice may communicate with or through an end-user device (e.g., insteadof or in addition to the mobile hotspot access network).

The eighth example mode 570 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the eighth example mode 570 may be utilized forgathering and/or serving data (e.g., in a delay-tolerant networkingscenario), providing peer-to-peer communication through the mobilehotspot access network (e.g., between clients of a single Mobile AP,between clients of respective different Mobile APs, etc.), etc. Inanother example scenario, the eighth example mode 570 may be utilized ina scenario in which vehicle-to-vehicle communications are prioritizedabove vehicle-to-infrastructure communications. In yet another examplescenario, the eighth example mode 570 may be utilized in a scenario inwhich all infrastructure access is lost (e.g., in tunnels, parkinggarages, etc.).

Note also that the eighth example mode 570 may be utilized in a scenarioin which the backbone provider network, local infrastructure providernetwork, and/or fixed hotspot access network are normally available butare currently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

As shown and discussed herein, it is beneficial to have a genericplatform that allows multi-mode communications of multiple users ormachines within different environments, using multiple devices withmultiple technologies, connected to multiple moving/static things withmultiple technologies, forming wireless (mesh) hotspot networks overdifferent environments, connected to multiple wired/wirelessinfrastructure/network backbone providers, ultimately connected to theInternet, Cloud or private network infrastructure.

FIG. 6 shows yet another block diagram of an example networkconfiguration, in accordance with various aspects of the presentdisclosure. The example network 600 may, for example, share any or allcharacteristics with the other example networks and/or networkcomponents 100, 200, 300, 400, 500-570, 700, 800, 900, 1000, 1100, and1200 discussed herein. Notably, the example network 600 shows aplurality of Mobile APs (or OBUs), each communicatively coupled to aFixed AP (or RSU), where each Mobile AP may provide network access to avehicle network (e.g., comprising other vehicles or vehicle networks,user devices, sensor devices, etc.).

FIG. 7 shows still another block diagram of an example communicationnetwork 700, in accordance with various aspects of the presentdisclosure. The example network 700 may, for example, share any or allcharacteristics with the other example networks and/or networkcomponents 100, 200, 300, 400, 500-570, 600, 800, 900, 1000, 1100, and1200 discussed herein. Notably, the example network 700 shows aplurality of vehicles (or Mobile APs, or MAPs, or OBUs) 752, 754, 756,and 758, each communicatively coupled to a Fixed AP (or RSU) 742, 744,and 748 and/or a cellular network 706, where each Mobile AP may providenetwork access to a vehicle network (e.g., comprising other vehicles orvehicle networks, user devices, sensor devices, etc.), for example aWi-Fi network to which end user devices may connect, with whichcommunication with sensors may be performed, etc. The example network700 may also, for example, comprise a plurality of Network Controllers732, 734, and 738. The example network 700 may also, for example,comprise any of a variety of interconnected networks (e.g., PrivateNetworks 702, the Internet 704, Telecommunication Networks 706, etc.).One or more servers of the Cloud may, for example, be accessible viaCloud APIs 760.

The Mobile APs 752, 754, 756, and 758 may, for example, becommunicatively coupled to various sensors (e.g., always, as the MobileAPs travel within range of such sensors, etc.). For example, in theexample scenario shown in FIG. 7, a first MAP 752 is communicativelycoupled to a first sensor 771 (e.g., Sensor 1) and a set of sensors 772(e.g., Sensor 2, Sensor 3, Sensor 4, and Sensor 5), which may forexample be co-located; a second MAP 754 is communicatively coupled to asixth sensor 773; and an M^(th) MAP 758 is communicatively coupled to aseventh sensor 774. The Mobile APs may, for example move in and out ofcommunication range of the various sensors. The Mobile APs may, forexample when in-range of such sensors, gather information from suchsensors in a power-efficient and network-efficient manner, many examplesof which are provided herein.

As discussed herein, sensors can economically measure a large varietyparameters, for example from environmental conditions like temperature,humidity, barometric pressure, insulation, noise, pollution levels, gas,particles, rain, etc., to the behavior of people and objects. Deployingsensors can however be expensive, particularly when they require a fixedconnection to a power source and/or a wired link for communication. Toefficiently collect data from sensors and transport the collected datato the Cloud, a communication network in accordance with various aspectsof this disclosure (e.g., a network or Internet of Moving Things) may beutilized as a communication backbone. For example, in an exampleimplementation, a vehicle equipped with a mobile access point (or MobileAP, or MAP, or OBU) can communicate with a sensor as the vehicle passesor parks nearby. Collected sensor data can be stored and processed andmade available to/from the Cloud (e.g., via APIs or other interfaces).Additionally, collected sensor data may be gathered and processedlocally (e.g., at the Mobile AP). Non-limiting examples of systems andmethods for collecting sensor data, for example in a network of movingthings, are provided in U.S. Provisional Application No. 62/222,135,titled “SYSTEMS AND METHODS FOR COLLECTING SENSOR DATA IN A NETWORK OFMOVING THINGS,” filed on Sep. 22, 2015, the entire content of which ishereby incorporated by reference in its entirety.

In accordance with various aspects of the present disclosure, systemsand methods are provided that utilize one or more mobile access pointsto gather (or harvest) data from sensors. Various aspects of thisdisclosure provide for cooperation among APs and sensors to optimize thedata collection in various ways (e.g., maximizing throughput, minimizinglatency, maximizing reliability, adjusting the data collectionparameters such as resolution and/or QoS rules and/or sample interval,utilizing geographical information for sensor data collection planning,minimizing unnecessary redundancy in data collecting, etc.). Such datacollection may, for example, be adjusted dynamically in response tovarious conditions (e.g., weather, time-of-day, day-of-year, externalevents, security issues, emergency conditions, client and/or operatordirectives, etc.).

A communication network, in accordance with various aspects of thepresent disclosure, may then transport the collected sensor data to theCloud or any other node in various ways (e.g., utilizing any of avariety of communication technologies, utilizing any of a variety ofpathways through the network, utilizing delay-tolerance networking,utilizing opportunistic uploads for example via Wi-Fi networks,communicating such data in accordance with various QoS rules, etc.).

In a network in which mobile nodes (e.g., Mobile APs, user devices,etc.) are utilized to collect (or gather) sensor data, sources of suchdata (e.g., stationary and/or mobile sensors, other data sources, etc.)may be numerous and the volume of such data may be great. Over time, itis expected that the network of moving things will result in a rapidincrease in the amount of sensor data collected (e.g., in a metropolitanarea). Such increases in the volume of data, however, present datacollecting, storage, processing, and communication challenges.

In an example scenario in which there is too much data for one or moreMobile APs to handle, some data may be lost (e.g., not collected at all,only partially collected, collected with errors, etc.). Other data maybe collected, but not in a timely manner. For example, a Mobile AP mayfail or be overwhelmed if operated autonomously in accordance with aninflexible data collection strategy (or plan). Fortunately, a network ofmoving things provides the flexibility and/or adaptability to respond tounforeseen system disturbances, data collecting needs, system and/orsensor topology changes, etc. Such flexibility may, for example, providefor the necessary or desired amount of data to be collected.

In an example implementation, data collection by the network of movingthings (or any component thereof) may initially be operated inaccordance with an original plan, for example corresponding to aparticular vehicle, vehicle route for a shift (e.g., for a minute, foran hour, for a day, for some other period of time, etc.), etc. Theoriginal plan may then, for example, be adjusted or adapted in real-timebased on any of a variety of conditions that may be deemed significantenough to modify the original plan. FIG. 8 shows a non-limiting exampleof such operation. It should be noted that the scope of this disclosureis not limited by characteristics of such specific example nor by anyspecific examples discussed herein.

FIG. 8 shows a flow diagram of an example method 800 of collecting datain a network of moving things, in accordance with various aspects of thepresent disclosure. Any or all aspects of the example method 800 may,for example, be implemented in any of a variety of network componentsdiscussed herein (e.g., in a Mobile AP or OBU, in a Fixed AP or RSU, ina mobile user device, etc.). Additionally for example, the functionalityof the example method 800 may be distributed among any two or more ofthe network components discussed herein.

The example method 800 may, for example, begin executing at block 805.The example method 800 may begin executing in response to any of avariety of causes or conditions. For example, the method 800 may beginexecuting in preparation for a vehicle comprising a Mobile AP beginninga route or shift. Also for example, the method 800 may begin executingon a timed schedule (e.g., an absolute start and/or update time,periodically with a consistent and/or varying period, in response to auser command, while a vehicle is being maintained, while a vehicle isparked in a garage, in response to a power-up condition, in response toan engine starting, in response to a vehicle beginning to move, etc.).Accordingly, the scope of this disclosure is not limited bycharacteristics any particular initiating cause or condition.

The example method 800 may, at block 810, comprise determining a datacollection plan. Block 810 may comprise determining a data collectionplan (e.g., for a Mobile AP, Fixed AP, etc.) in any of a variety ofmanners, non-limiting examples of which are provided herein. Forexample, block 810 may comprise requesting and/or receiving a datacollection plan from a central controller (e.g., an applicationexecuting on a server in the Cloud, an application executing on anyother communication network node, etc.). In an example scenario, acentral controller (e.g., with a model of the entire network and/or withknowledge of all data collection needs) may communicate a datacollection plan to all nodes involved in such collection. Suchcommunication (or propagation) may, for example, comprise a push systemand/or pull system.

Also for example, block 810 may comprise retrieving (or otherwiseaccessing) a data collection plan stored in an on-board memory. In anexample implementation, a node may comprise utilizing a prior datacollection plan (e.g., as a baseline and/or default plan), for example aplan from a previous shift, a plan from a previous day, a plan from whenthe present route was most recently run, etc. Additionally for example,block 810 may comprise retrieving a data collection plan associated witha route that the node (e.g., comprising a Mobile AP) is to follow. Forexample, a database of fleet vehicle routes and respective datacollection plans may be maintained, and accessed by vehicles (or theirMobile APs) when a route is assigned.

Additionally for example, block 810 may comprise receiving a datacollection plan from a peer node. For example, a Mobile AP may receive adata collection plan from another Mobile AP, for example a Mobile APthat has most recently ran a route. In such a manner, the Mobile AP mayalso receive a status for the received data collection plan thatindicates data that was recently collected and might not need to becollected by the Mobile AP (e.g., during this run).

In a further example, block 810 may comprise a plurality of nodes (e.g.,Mobile APs and/or Fixed APs, etc.) selecting and/or negotiating whichnode will perform particular data collections. For example, a pluralityof vehicle nodes (e.g., Mobile APs, etc.) that plan to be passing by(and/or are capable of passing by) a particular data source during aperiod of time may communicate with each other to determine which nodewill collect the data from such source. For example, a plurality of suchnodes may communicate with each other regarding remaining resourcecapacity (e.g., memory resources, processing resources, communicationresources, etc.) and determine among themselves which of such nodes hasthe most remaining capacity and should perform the data collection. Thenodes may make this decision without central control. Note, however,that a central controller may also make the determination andcommunicate such determination to the relevant node(s). Suchcommunication and/or determination may occur before running a routeand/or during running a route (e.g., as a Mobile AP is approaching orexpecting to approach a known sensor location). Also note that a nodemay make a data collection determination autonomously, for example ifthe node realizing the need for the data collection and/or datacollection modification has enough excess capacity that it is notconcerning enough to involve other nodes.

FIG. 9 shows a block diagram of an example AP system for interfacingwith a sensor system, in accordance with various aspects of the presentdisclosure. FIG. 9, for example, shows various communication linksbetween various network nodes (e.g., Cloud nodes, fixed infrastructurenodes, mobile infrastructure nodes, sensors, etc.) that may communicateto determine a data collection strategy. The example network 900comprises the Cloud 910, which includes a computer (or server) 901. Theexample network 900 also comprises a Fixed AP Infrastructure 920 thatcomprises a first Fixed AP 902 and a second Fixed AP 903 that iscommunicatively coupled to the Cloud 910. The example network 900additionally comprises a Mobile AP network 930 that comprises aplurality of Mobile APs 904-908 that are directly and/or indirectlycommunicatively coupled to the Fixed APs 902 and 903. The example MobileAP 907 is shown communicatively coupled to one or more Sensors 909 ofthe Sensor Environment 940.

Returning to FIG. 8, as discussed herein, a data collection plan may bedetermined based on any one or more of a variety of factors. In anexample implementation, an overall cost function may be minimized indetermining an optimal data collection plan. The discussion hereinprovides various examples of factors that may be considered indetermining such plan (or strategy). It should be noted that the factorsdiscussed herein do not represent an exclusive list, and other factorsmay also be considered (e.g., instead of and/or in addition to thefactors discussed herein).

The data collection plan may, for example, be determined based at leastin part on network and/or sensor topology. For example, the locations offixed (or generally fixed) sensors may be known or predictable, thelocation of Fixed AP nodes may be known, the travel patterns of MobileAPs may be known, etc. The data collection plan may thus be based onsuch knowledge, for example, correlating sensor data collecting goals(e.g., data collecting times, communication times, etc.) with potentialdata collecting nodes that are or are predicted to be available for thedata collecting. As discussed herein, various data sources may be fixed,mobile, generally fixed but movable, etc. In such examples, a mobiledata source may be predictably located, at least with a high enoughdegree of certainty to establish an initial data collection plan. Alsoas discussed herein, even a so-called fixed topology may change, so adata collection system in accordance with various aspects of thisdisclosure may adapt to fit the changing topology.

The data collection plan may also, for example, be determined based onhistorical information. For example, after a period of running, asubstantial portion of the data collection operations may reach a steadystate, in which each of a set of data gatherers (e.g., Mobile APs, etc.)may typically interact with a respective set of sensors (e.g., on aday-to-day basis). For example, a 06:15 bus might always interact withthe garbage can sensors on its route (e.g., leaving the 06:30 bus and/orother subsequent buses as back-ups if the 06:15 bus misses some data).In such a scenario, barring a real-time disruption in the operation ofthe 06:15 bus and/or in the real-time context in which such bus isoperating, the 06:15 bus may always be assigned to the collection of thegarbage can sensor data. Note that, as discussed herein, historical andpresent operational information (and any data discussed herein) may befed back into the system to adapt system models (e.g., system modelsutilized for determining the data collection plan, models for reactingto particular system operational disturbances or anomalies, etc.).

In another example, if a vehicle (e.g., running a particular route,operating during a particular time period, operating on a particulartype of day, etc.) is historically associated with low resource (e.g.,memory, processing, communication bandwidth, energy, etc.) utilization,a data collection plan may assign a relatively large amount of sensordata gathering activity to such vehicle (or Mobile AP). Alternatively,if a vehicle (e.g., running a particular route, operating during aparticular time period, operating on a particular type of day, etc.) ishistorically associated with high resource (e.g., memory, processing,communication bandwidth, energy, etc.) utilization, a data collectionplan may assign a relatively small amount of sensor data gatheringresponsibility to such vehicle, for example assigning such datagathering to other vehicles, fleets, times of day, etc.

As discussed herein (e.g., in the discussion of network topology, etc.)a data collection plan (or strategy) may also be based, at least inpart, on expected contact time between a data gatherer (e.g., a MobileAP, etc.) and a data source (e.g., a sensor system). For example, duringa period of data gathering need, a set of one or more Mobile APs mayeach have a respective expected effective communication contact timewith a data source (e.g., based on communication range, vehiclelocation, vehicle speed, expected vehicle trajectory, sensor location,expected communication data rate at a location, etc.). In an examplescenario in which only one data gatherer is expected to be able toperform the data gathering, the data plan may assign such data gathererto collect the data from such data source. In an example scenario inwhich a plurality of data gatherers are expected to be able to performthe data gathering, any or all of the other factors discussed herein maybe utilized to select the assigned data gatherer from the set (e.g.,identifying one or more data gather(s) that minimize an overall costfunction, etc.). In another example, for example in which any singledata gatherer is not expected to be able to collect all of the data fromthe source, a plurality of data gathers may be assigned to collect thedata in aggregate, each collecting a respective portion. Note that asdiscussed herein, the nature of the data gathered may also be adapted(e.g., so that one gatherer may collect all of the necessary data,etc.).

A data collection plan may also be determined based, at least in part,on the amount of data to be collected (or processed, communicated, etc.)and/or on the amount of resources available to the data collecting node(e.g., memory resources, processing resources, energy resources,communication resources, etc.). For example, in an example scenario inwhich a first Mobile AP does not presently comprise the resources (e.g.,communication resources, processing resources, memory resources, energyresources, etc.) and/or will not be within communication range of thedata source long enough to communicate the data, the data collection maybe passed to a second Mobile AP (e.g., instead of and/or in addition tothe first Mobile AP). For example in an example scenario in which thedata collection memory and/or communication resources for a Mobile APare already allocated for other uses (e.g., for collecting data fromother sources), the data collection for a particular source by which theMobile AP is passing may be assigned to another Mobile AP, oralternatively the Mobile AP may be assigned to the data collection whileanother data collection previously assigned to the Mobile AP isre-assigned to another Mobile AP. Note that communication bandwidthresources between the data collecting node and the data source, thecommunication bandwidth resources between the data collecting node and apeer data collecting node, the communication bandwidth resources betweenthe data collecting node and the network infrastructure, and/or thecommunication bandwidth resources between the data collecting node andan ultimate destination node for the collected data may be considered.

In an example scenario in which it is determined that a Mobile AP isunable to collect data from a particular sensor and communicate thecollected data to a Cloud application within a required amount of time,such data collection being assigned to another data collecting node (orfor example to additional nodes to perform an aggregate collection andcommunication of the data). In other words, in a scenario in which it istime-critical that collected data be communicated to a recipient, thedata collection plan may be based, at least in part, on the respectivelatencies of different candidate data collecting nodes.

The data collection plan may, for example, be based at least in part ondata priority. For example, in an example implementation, datacollection responsibilities (or assignments) for the relativelyhigh-priority data are assigned to data collecting nodes (e.g., MobileAPs, etc.) before data collection duties for the relatively low-prioritydata. As discussed herein, however, the priorities may changedynamically in response to real-time needs or conditions.

For example, in an example scenario in which a Mobile AP is on-board awaste collection vehicle, data collection associated with waste pick-up(e.g., garbage can fullness and location, etc.) may have a relativelyhigh priority, while data from other sources (e.g., street cameras, userdevices, etc.) might have a relatively low priority. Also for example,in an example scenario in which a Mobile AP is on-board a publictransportation vehicle, data from sources associated with vehicle and/orpassenger safety may have a relatively high priority (in general), whiledata from other sources (e.g., outdoor temperature sensors, streetcameras, etc.) may have a relatively low priority.

The data collection plan may additionally, for example, be based atleast in part on time of day, day of the week, type of day, etc. Forexample, during rush hour, data collection resources may be allocatedtoward traffic management sensor systems and away from garbage cansensors. In another example scenario, when gathering data on a day priorto a waste pick-up data for garbage, data collection resources may beallocated to garbage can sensor collection as a high priority. Asdiscussed herein, historical data may be utilized when developing thedata collection plan, which may be correlated to time-of-day,day-of-week, type-of-day, etc.

The data collection plan may additionally, for example, be based atleast in part on importance of data accuracy (e.g., level of redundancy,amount of replication, etc.). For example, in an example scenario inwhich data accuracy is particularly important, a data collection planmay be established that utilizes multiple data collecting nodes (e.g.,Mobile APs, etc.) to collect the same data from a source, in a redundantmanner. Also for example, in a scenario in which data errors aregenerally acceptable, the data collection plan may generally specifythat only one Mobile AP shall attempt to collect the data and/or onlymake one attempt per day at collecting the data.

The data collection plan may further, for example, be based at least inpart on load-balancing. For example, an overall goal for the datacollection plan (or strategy) may be to maintain each data collectingnode operating in a state that is comfortably within its capability, forexample to maintain the ability of each data collecting node to increaseits performance in response to real-time events and/or other changing orunexpected conditions.

The previous discussion generally addressed the determination of thedata collection plan in terms of the allocation of data collectionresponsibilities among the data collecting nodes. Any or all of thepreviously discussed factors may be analyzed to determine thecharacteristics of the collected data, the frequency (or regularity)with which such data is collected, whether the data is going to bepresently collected, etc.

For example, in any of the example scenarios discussed herein, if it isdetermined that a data collecting node does not have the resourcesavailable to collect all of the data desired for a collection (or costfunction analysis determines that all of the necessary resources tocollect all of the data should not presently be allocated to suchcollection), the characteristics of the collected data may be alteredfor the data collection strategy. For example, the resolution of thedata may be modified (e.g., utilizing a lower number of bits torepresent data values, utilizing a lower number of video blocks orpixels, etc.). Also for example, a type of data encoding may be modified(e.g., switching from a lossless to a lossy encoding strategy, switchingfrom a lossy to a more lossy encoding strategy, utilizing errordetection codes instead of error correction codes, eliminating errorcorrection and detection codes, etc.). Additionally for example, thetemporal resolution of the data may be altered. For example, a lowernumber of camera and/or audio frames may be collected.

In general, block 810 comprises determining a data collection plan (orstrategy) for a node. Accordingly, the scope of various aspects of thisdisclosure should not be limited by characteristics of any particularmanner of determining a data collection plan. Note that in various otherexample implementations, a node may collect (or gather) data in acompletely reactive manner, for example collecting data whenever asource of data (e.g., a sensor) is encountered for which data should begathered.

The example method 800 may, at block 820, comprise collecting (orgathering) data from various sources (e.g., any of a variety of sensors,examples of which were presented herein). Block 820 may, for example atleast initially, comprise collecting data from the data sources inaccordance with a known and/or predictable strategy. Such collecting ofdata may be performed in any or a variety of manners. For example,various non-limiting examples of such data collection (e.g., includingbut not limited to communication between Mobile APs and data sources)are provided in U.S. Provisional Application No. 62/222,135, titled“SYSTEMS AND METHODS FOR COLLECTING SENSOR DATA IN A NETWORK OF MOVINGTHINGS,” filed on Sep. 22, 2015, the entire contents of which are herebyincorporated by reference.

Block 820 may, for example, comprise immediately communicating, storing,and/or processing the collected data. For example, block 820 maycomprise immediately communicating time-sensitive data to a recipient.Such a recipient may, for example, comprise an application executing atthe node, an application executing at another node (e.g., a server inthe Cloud, a network controller, a network dashboard application, etc.).In an example scenario in which the collected data is somewhat delaytolerant, block 820 may comprise storing such collected data in a memoryand communicating such collected data to a recipient when convenient(e.g., when communication bandwidth is freely available, etc.). Inanother example scenario in which the collected data is delay tolerantwith no significant real-time communication needs, block 820 maycomprise storing the collected data in a memory for communicationsubstantially later (e.g., when a vehicle reports back to a garage orstation, etc.). In general, block 820 may comprise communicating and/orstoring the collected data. Accordingly, the scope of this disclosureshould not be limited by characteristics of any particular manner ofperforming such communication and/or storing.

Block 820 may also, for example, comprise performing any of a variety oftypes of processing on the collected data. For example, block 820 maycomprise processing collected sensor data to determine various metrics,where for example such metrics may be communicated rather than or inaddition to the raw collected data. Also for example, block 820 maycomprise compressing raw sensor data for efficient communication via thecommunication network infrastructure. Additionally for example, block820 may comprise performing error correction and/or detection on thecollected data. In an example scenario, block 820 may comprisedetermining whether the data was adequately collected, for exampledetermining whether the node should make another attempt and/or requestanother node to make another attempt. In general, block 820 may compriseprocessing collected data. Accordingly, the scope of this disclosureshould not be limited by characteristics of any particular manner ofperforming such processing.

The example method 800 may, at flow control block 830, comprisedetermining whether the data collection has been completed. If so, thenblock 830 may direct execution flow of the example method 800 to block895 for continued operation. If not, then block 830 may direct executionflow of the example method 800 to block 840.

At block 840, the example method 800 may comprise determining if anydetected condition and/or event has occurred that may warrant a changein the data collection plan (or strategy). Any of a variety ofconditions may, for example, justify modification of the data collectionplan, many non-limiting examples of which are provided herein.

As discussed herein, though not necessary in all examples, one or moredata collecting nodes (e.g., Mobile APs, Fixed APs, AP client devices,etc.) may operate in accordance with a data collection plan that isrelatively stable. The data collection environment may, however, havechanged. For example, many example factors on which a data collectionstrategy may be developed are discussed herein. Any of such factors maychange, sometimes without notice. Data collection systems and methods inaccordance with various aspects of this disclosure may flexibly react tochanging conditions and/or conditions being different than expected.Note that other factors, for example most emergency events, might not bepredictable and thus might not be considered in developing various datacollection plans.

At block 840, a changing or unexpected condition may be detected in anyof a variety of manners. For example, a data collecting node operatingin accordance with the example method 800 may detect a condition,another data collecting node may detect a condition and communicate thisto the data collecting node (or another node), the data collecting nodemay receive a signal from any of a variety of sources indicating that acondition has changed, etc. Though many examples are presented herein,the scope of this disclosure is not limited by characteristics of suchexamples. In an example implementation, block 840 may comprise receivinginformation of various detected conditions from any sensor, from adriver (e.g., human or autonomous vehicle control system), from an OBDsystem, from another node of the network, etc.

An example condition may, for example, comprise the occurrence of anemergency situation. For example, block 840 may comprise receiving anindication that an emergency condition exists and that the datacollection plan may need to be modified. For example, in a public safetyemergency, the priority of street camera information (at least in aparticular geographic area) may be elevated to the highest level andother data collection may be de-prioritized. In such a scenario, it maybe determined at block 810 that all or a substantial portion of a MobileAP' s data collection, processing, and/or communication resources are tobe dedicated to the collection and communication of street camerainformation to the Cloud (e.g., to an emergency services commandcenter). Also for example, in an example scenario in which a seriousautomobile accident occurs, it may be determined (e.g., at block 810)that camera and microphone sensor information in a one-block radius ofthe accident, and/or along emergency vehicle routes to and from theaccident take precedence over all other types of data presently being orplanned to be collected. In such a scenario, it may be determined atblock 810 that since the Mobile AP is in or near the geographical areain which the camera and microphone sensor information has been elevatedto high-priority status, the Mobile AP must dedicate all or asubstantial portion of its resources to the collection and communicationof sensor information from cameras and/or sensors within range. FIG. 10provides an illustration, for example in comparison to FIG. 9, in whichthe camera sensor has been elevated in priority relative to othersensors and is communicating data to multiple Mobile APs. For example,as shown in the labeled wireless communication links in FIG. 9, therespective data gathering associated with the camera sensor and withanother sensor are at a same priority. As shown in the labeled wirelesscommunication links in FIG. 10, however, the data gathering associatedwith the camera sensor has a higher priority than the data gatheringassociated with the other sensor. This relative prioritization isadaptable based on real time conditions.

Another example of an emergency condition may include an operator of avehicle (e.g., a local human operator, an autonomous vehicle controlsystem, a remote human operator, etc.) associated with the Mobile APpressing an emergency button (or generating an emergency signal), forexample because of a detected accident, a crime, a public safetysituation, etc. In such a scenario, block 840 may direct execution flowof the example method 800 to block 810 at which the data collectionstrategy may at least temporarily be modified to emphasize thecollection and/or communication of sensor data associated with thevehicle (e.g., vehicle operational sensors, vehicle cameras and/ormicrophones, sensors within range of the vehicle, sensors of userdevices within or within the range of the vehicle, etc.). Additionally,person-to-person communication resources between the vehicle operatorand a command center may similarly be designated high-priority, ascommunication resources between an automated vehicle control system anda command center or central controller.

Another example of a real-time condition that may cause modification toa data collection plan includes a detected traffic jam (e.g., a highdegree of vehicle density in an area, a low amount of vehicle movement,etc.). For example, detected bad traffic conditions may increase thepriority of traffic sensors (e.g., camera sensors, emission sensors,intersection vehicle sensors, noise sensors, radar sensors, etc.).

It is reiterated that the conditions (e.g., bad traffic conditions,etc.) need not be detected by a particular node operating in accordancewith the example method 800. Such conditions may be detected by any nodein the network, including infrastructure nodes, access points, AP clientdevices, sensor systems in communication with the network, governmentcommand centers, etc. For example, such information may be propagated tothe node or nodes that manage the data collection strategy (e.g., to anindividual node, to a set of nodes determining data collection strategytogether, to a central controller determining data collection strategy,etc.).

Another example condition may, for example, include a weather condition.For example, when a severe weather condition is detected (e.g., detectedby a weather sensor in communication with a node of the network,detected by receiving a message from a weather service, etc.), weatherand/or driving condition sensor data may receive a heightenedprioritization. For example, in a scenario in which freezing rain hasbeen detected or is forecast, a data collection plan (or strategy) mayprioritize the collection of data from slippage detection sensors,accident detection sensors, temperature and/or precipitation sensors,etc. Also for example in a scenario in which a tornado warning has beenissued, a data collection plan may prioritize the collection of datafrom temperature and pressure sensors, from sky cameras, etc.

A further example condition may, for example, include poor roadconditions. For example, when one or more vehicles carrying Mobile APsdetect slippery road conditions, excessively large pot holes, etc., adata collection plan may for example prioritize the collection ofsensors associated with road conditions (e.g., vehicle tire slippagedetectors, shock sensors or accelerometers, position sensors, etc.).

An example condition may, for example, include detection of anunexpected data source. For example, when a data collecting nodeencounters an unexpected data source that is in need of servicing, suchan encounter may result in a modification to the data collection plan(e.g., which might have been developed without considering theunexpected data source). For example, a new camera, new set of wastesensors, new set of environmental sensors, etc. may have been installedalong a route traversed by a public transportation vehicle carrying aMobile AP that collects sensor data. If collecting data from the newlydetected sensors has a substantial impact on the resource utilization ofthe Mobile AP, a new data collection plan (e.g., in which at least someof the data gathering responsibilities of the Mobile AP are transferredto another AP, in which data collection for the new sensor is assignedto another Mobile AP, etc.) may be formed.

Another example condition may, for example, include an unexpected amountof data, for example from a known data source. For example, a datacollection plan (or strategy) may have been developed expecting aparticular amount of data from a particular data source. During theprocessing of collected data from the source, a data collecting node maydetermine that the data source (e.g., a security camera, trafficmonitor, etc.) has substantially more data to communicate than expected.In such an example scenario, execution of the example method 800 mayflow from block 840 to block 810, at which the data collection plan(e.g., for the data collecting node and/or other data collecting nodes)may be modified.

Still another example condition may, for example, include a changingtime constraint associated with a type of data. For example, a datacollection plan may have been developed assuming that data from a sensoris delay-tolerant. Conditions may, for example, have changed such thatthe data has been characterized as time critical and in need ofimmediate communication, taking priority over other information that isalso in need of communication. In such an example scenario, block 810may comprise adjusting the data collection plan in any of a variety ofmanners (e.g., modifying an amount of other data to be communicated,shifting data collecting and/or communication responsibilities to otherdata collecting nodes that have the necessary collecting and/orcommunication resources, sharing the data collection responsibilitiesbetween a plurality of nodes, etc.).

An example condition may, for example, include detected vehicleconditions (e.g., by on-board diagnostic sensors, etc.). For example, inan example scenario in which data associated with on-board diagnosticsensors is generally gathered and communicated at a low rate, detectionof an anomaly in the operation of the vehicle in which a Mobile AP iscarried may cause data collection priorities to emphasize collection andcommunication of vehicle sensor data (e.g., to a diagnostic center foranalysis to determine whether a replacement vehicle should bepreemptively prepared and dispatched, to schedule vehicle maintenanceactivities, etc.). In such a scenario, other data collections that arebeing performed or were going to be performed by the vehicle may betransitioned to other vehicles.

Another example condition may, for example, include a different clientcount and/or different client resource utilization than expected. Forexample, in an example scenario in which a public transportation vehicletypically services a particular number of clients utilizing a particularamount of communication bandwidth, a surge in such utilization mayadversely impact a Mobile AP's ability to gather and/or communicatesensor data. In such a scenario, data collection responsibilities may betransferred to other Mobile APs, the bandwidth allocated to publicutilization versus sensor data gathering may be adjusted, etc.

Yet another example condition may, for example, include a failure in oneor more nodes (e.g., a data collection node, intermediate communicationnode, etc.) of the system. For example, in an example in which a MobileAP of a vehicle has apparently failed and/or an intermediatecommunication node between such Mobile AP and a destination for thecollected data has failed, another Mobile AP and/or a central controllermay determine that the failure has occurred, and shift the datacollection responsibilities for the Mobile AP to one or more otherMobile APs, adjust the characteristics of the data to be gathered toreduce the resource burden on the other Mobile APs if necessary, etc.

Another example may, for example, include detected data congestion inthe network. For example, a data collection plan may have been developedassuming (e.g., based on historical data rates) a particular data ratefor communicating camera sensor data upstream to a traffic controlsystem. In an example scenario in which the actual data rate (e.g., dueto network congestion, node failures, etc.) is substantially less thanexpected, the ability for the data collecting node to communicate thecollected data and/or other data may be substantially decreased,resulting in inadequate quality of the data collection service. Inresponse to a detected communication issue, the data collection plan maybe modified, for example utilizing different data pathways, shiftingcommunication responsibilities or pathways to other nodes, etc.

Many of the examples present herein include the shifting of datagathering and/or communication responsibilities from a first datacollecting node to one or more other data gathering nodes. In any ofsuch scenarios, a decision may also be made to simply skip a particulardata collection, which may be performed at a later time and/or by adifferent data collecting node. Other examples discussed herein includedthe determination that collecting and/or communicating at a reducedresolution may be acceptable, at least temporarily. In any of thescenarios discussed herein, instead of (or in addition to) shifting datagathering and/or communicating responsibilities to another node,particular data gathering responsibilities for the data collecting nodemay be reduced in magnitude by adjusting the resolution (e.g., valueresolution, temporal resolution, etc.) of the particular data beingcollected. Note that such adjusting may include the Mobile APcommunicating with the sensor to adjust the data being sent by the datasource, for example instead of the Mobile AP ignoring data that iscommunicated by the source.

Though many examples of detected conditions have been presented herein,as well as many example responses to such conditions, the scope of thisdisclosure is not limited to such examples.

Note that although block 840 (and other blocks) of the example method800 are shown in particular locations in the example flow diagram, thescope of this disclosure is not limited to such flow order. For example,the functionality of block 840 may be performed at any time (e.g., inresponse to a detected condition or event, etc.).

If, at block 830, it is determined that the data collection is complete,then execution of the example method 800 flows to block 895 forcontinued operation. Such continued operation may comprise any of avariety of characteristics. For example, block 895 may comprisedirecting execution flow of the example method 800 to any previous block(or portion thereof) and/or any other method block (or portion thereof)discussed herein. Also for example, block 895 may comprise communicatinginformation describing the difference between an originally planned datacollection session and an actually implemented data collection sessionto one or more other nodes of the system, for example for system modelupdating, etc.

As discussed herein, any one or more of a variety of nodes (e.g., MobileAPs, Fixed APs, central controllers, Cloud-based applications, datacollection application, network dashboard applications, etc.) mayoperate to determine data collecting plans (or strategies) for one ormore nodes in the network. The following example is presented in thecontext of a single node, which may for example be a central controlleror Cloud-based application, which serves as a destination for collecteddata and also as a central planner for the data collection activitiesfor the network. Though this example is presented in such context, itshould be understood that the example may be implemented in adistributed manner by a plurality of different nodes or servers orapplications.

FIG. 11 shows a flow diagram of an example method 1100 of collectingdata in a network of moving things, in accordance with various aspectsof the present disclosure. The example method 1100 may, for example,share any or all characteristics with any other methods discussed herein(e.g., the example method 800 shown in FIG. 8 and discussed herein,etc.). Also, any or all portions of the example method 1100 may, forexample, be implemented by any of the network nodes discussed herein(e.g., a Mobile AP node or OBU, a Fixed AP node or RSU, any networkinfrastructure node, a Cloud server, an AP client device, a mobile userdevice, etc.). In an example implementation, the example method 1100 maybe implemented by one or more central data collection controllerapplications being run by one or more servers in the Cloud.

The example method 1100 may, for example, begin executing at block 1105.The example method 1100 may begin executing in response to any of avariety of causes or conditions. For example, the method 1100 may beginexecuting in preparation for any vehicle comprising a Mobile APbeginning a route or shift. Also for example, the method 1100 may beginexecuting on a timed schedule (e.g., an absolute start and/or updatetime, periodically with a consistent and/or varying period, etc.), inresponse to a user command, while a vehicle is being maintained or mostvehicles in a fleet are being maintained, while a vehicle is parked in agarage or most vehicles in a fleet are parked in a garage, in responseto a power-up condition, in response to an engine starting, in responseto one or more vehicles beginning to move, in response to a signalreceived from another application, etc. The example method 1100 may, forexample, continually execute. Accordingly, the scope of this disclosureis not limited by characteristics of any particular initiating cause orcondition.

The example method 1100 may, at block 1110, comprise determining a datacollection plan. Block 1110 may, for example, share any or allcharacteristics with the example block 810 discussed herein. Block 1110may, for example, determine a data collection plan based on any or allof the factors discussed herein. In an example implementation, block1110 may comprise determining a data collection plan for all Mobile APs(and/or other nodes or devices) in the network that have data collectioncapability. Also for example, block 1110 may comprise determining a datacollection plan for all data collecting nodes of a particular fleet(e.g., a bus fleet, a waste management fleet, an emergency servicesfleet, a harbor fleet, etc.).

At block 1120, the example method 1100 may comprise propagating one ormore data collection plans. Block 1120 may comprise propagating the datacollection plan(s) in any of a variety of manners. For example, block1120 may comprise communicating individual data collection plans torespective data collecting nodes in a unicast manner. Also for example,block 1120 may comprise communicating a data collection plan for alldata collecting nodes in a fleet of vehicles to a fleet controller node(or application), which may then be distributed by one or more othernodes.

Block 1120 may, for example, comprise distributing data collection plansin a push or pull manner. For example, in an example scenario, uponstartup of a Mobile AP (e.g., a vehicle being prepared for operating ashift, a Mobile AP reset or reboot, a timer expiration, etc.), a MobileAP may request a data collection plan from a server (or database) ofsuch plans. Block 1120 may then comprise responding to such a request.In another example scenario, block 1120 may comprise propagating thedata collection plans without being requested to do so (e.g.,periodically, at a scheduled time, when a data collection plan haschanged, etc.).

In an example implementation in which the data collection plan iscontinually adapting, a change in a data collection plan (or a portionthereof) may trigger immediate propagation of the data collection planto those data collecting nodes affected by the change. Such planupdating may, for example, occur periodically (e.g., hourly, daily,etc.) or may occur in real-time as a change is made. For example, in ascenario in which a data collection plan is adjusted in response to areal-time detected condition, many examples of which are providedherein, block 1110 may comprise modifying a data collection plan for oneor more data collecting nodes and immediately distributing the modifieddata collection plan to the affected data collecting nodes.

In general, block 1120 may comprise propagating a data collection plan.Accordingly, the scope of this disclosure is not limited bycharacteristics of any particular manner of performing such propagation.

The example method 1100 may, for example at block 1130, comprisereceiving and/or processing collected data from the data collectingnodes. In an example implementation, a node implementing the examplemethod 1100 may manage data collection planning and/or overall datacollecting. In an example scenario in which the method 1100 comprisesmanaging data collection planning and also receiving the collected data,the method 1100 may comprise monitoring the overall performance of thedata collection system, for example determining whether the datacollecting nodes are performing according to plan and making adjustmentsto the data collection plan if necessary.

The example method 1100 may, for example at block 1140, comprisereceiving information of conditions (or factors) related to the datacollection process (e.g., related to data source or sensor operation,network operation, environmental context, etc.). Many examples of suchconditions are provided herein, for example in the discussion of theexample method 800 of FIG. 8, etc.). For example and without limitation,such information may comprise information about any one or more of:vehicle information (e.g., location, vehicle velocity, vehicle route,vehicle operational health, etc.), sensor information (e.g., sensorlocation, sensor data communication needs, sensor communicationcapabilities, etc.), time information, day information, network topologyinformation, noise source information, information of Mobile APoperating conditions and/or resource availability, information of datapriority, information of data accuracy needs, information of dataresolution requirements, information of data collection timeconstraints, information of load balancing, information of node resourceavailability, emergency information, traffic density information,traffic road condition information, weather information, informationregarding an unexpected data source, information about an expected datasource not found, information regarding amount of data from a source,information about client numbers and/or bandwidth utilization,information about network node failure and/or underperformance,information about data congestion, information about nodes autonomouslyand/or in conjunction with peer nodes adapting data collectingresponsibilities, etc.

At block 1150, the example method 1100 may comprise determining whetherany of the received sensor data and/or any of the received informationof conditions warrants a change in the data collection plan (e.g., animmediate real-time change, a non-time-critical change, etc.). If it isdetermined at block 1150 that a change in the data collection plan isimmediately warranted (e.g., in response to an emergency condition, inresponse to a condition that causes immediate need of particularinformation, etc.), then execution of the example method 1100 flows backup to block 1110 for a re-determination of the data collection plan.

If no change (or no immediate change) to the data collection plan iswarranted, then execution of the example method 1100 may proceed toblock 1160 for the continued collection of data by the system. Note thatin a scenario in which a change to the data collection plan iswarranted, but not immediately warranted, execution flow of the method1100 may return to block 1110 at a later time (e.g., during off hours,between shifts, etc.) for a redetermination of the data collection plan(or strategy).

At block 1160, if it is determined that there remains data to becollected in accordance with the data collection plan, then executionflow of the example method 1100 returns to block 1130 for the continuedreceiving of collected data and/or information of conditions. If it isdetermined that the data collection has completed, then execution flowof the example method 1100 proceeds to block 1195 for continuedoperation.

Such continued operation may comprise any of a variety ofcharacteristics. For example, block 1195 may comprise directingexecution flow of the example method 1100 to any previous block (e.g.,block 1110 for a redetermination of data collection plan based on recentevents, etc.). Also for example, block 1195 may comprise analyzingvarious types of information (e.g., collected data, system performanceinformation, customer feedback, information of the detected conditions,historical information, etc.) to adjust one or more models on which thedetermined collection plan is based.

Such adaptive modeling may, for example, be useful to determine whetherdetected anomalies are not anomalies at all, but are actually modifiedor previously unknown aspects of the system or operating environmentthat should now be expected as the norm and included in upfrontplanning, rather than being reacted to. For example, changing network orsensor topology, traffic adjustments based on construction projects,waste container movement, a consistent change in communication linkbandwidth, vehicle scheduling changes, etc., may all justify modelchanges.

As explained herein, the example methods may be performed in one or moreof any of a variety of network nodes. A non-limiting example of anetwork and/or node implementation is provided at FIG. 12.

FIG. 12 shows a block diagram of various components of an examplecommunication network 1200 (e.g., a network of moving things) forinterfacing with a sensor system, in accordance with various aspects ofthe present disclosure. The example network 1200 may, for example, shareany or all characteristics with the other networks discussed herein(e.g., networks 100, 200, 300, 400, 500-570, 600, 700, 900, 1000, 1100,1200, etc.). Any or all of the components of the example network 1200may perform any or all of the method steps presented herein (e.g., ofthe methods 800, 1100, etc.).

The example network 1200 comprises a Cloud 1230, which in turn maycomprise any of a variety of servers and/or nodes executingapplications. An example Cloud-based Application 1235, or a pluralitythereof, is shown. In an example implementation, the Application(s) 1235may operate in accordance with the example method 1100 of FIG. 11. Forexample, one or more memory devices of a Cloud computer or server may,for example, comprise a non-transitory computer-readable medium thatcomprises software instructions that when executed by one or moreprocessors, cause the Cloud computer or server to perform any or all ofthe functionality discussed herein (e.g., with regard to the examplemethods 800 and 1100 discussed herein, etc.).

The example network 1200 also comprises a Mobile AP 1210, a secondMobile AP 1220, and a Fixed AP 1225. The example network 1200 furthercomprises one or more sensors 1240.

The example Mobile AP 1210 comprises a Network Communication Interface(I/F) Module 1211 that is operable to communicate with a communicationnetwork (e.g., infrastructure components, Cloud components, Fixed APs,etc.). The Network Comm I/F Module 1211 may, for example, operate tocommunicate in accordance with any of a variety of communicationprotocols (e.g., 802.11p, cellular, etc.). In an example scenario, theMobile AP 1210 utilizes the Network Comm I/F Module 1211 to communicatewith a server in the Cloud 1230 that is operating in accordance with theCloud-based Application(s) 1235. The Network Comm I/F Module 1211 may,for example, communicate with such server via a Fixed AP 1225 and/or anyof a variety of intermediate nodes. For example, any of the examplecommunication discussed herein between a Mobile AP and a Fixed AP,network infrastructure node, Cloud component, etc., may be performedutilizing the Network Comm I/F Module 1211.

The example Mobile AP 1210 comprises a Peer-to-Peer (P2P) CommunicationInterface (I/F) Module 1212 that is operable to communicate with peernodes (e.g., Mobile APs, etc.). The P2P Comm I/F Module 1212 may, forexample, operate to communicate in accordance with any of a variety ofcommunication protocols (e.g., 802.11p, cellular, Wi-Fi, etc.). In anexample scenario, the Mobile AP 1210 utilizes the P2P Comm I/F Module1212 to communicate with one or more other Mobile APs (and/or Fixed APs)in the network 1200. The P2P Comm I/F Module 1212 may, for example,communicate with a peer node 1220 directly, via an intermediate Fixed AP1225, via any one or more of a variety of intermediate nodes, etc. Forexample, any of the example communication discussed herein between aMobile AP and another Mobile AP, etc., may be performed utilizing theP2P Comm I/F Module 1212.

The example Mobile AP 1210 comprises a Sensor Communication Interface(I/F) Module 1213 that is operable to communicate with data sources(e.g., sensor systems, general data sources, etc.). The Sensor Comm I/FModule 1213 may, for example, operate to communicate in accordance withany of a variety of communication protocols (e.g., Wi-Fi, Bluetooth,UWB, cellular, wired interface, etc.). In an example scenario, theMobile AP 1210 utilizes the Sensor Comm I/F Module 1213 to communicatewith one or more other data sources (e.g., sensors, general datasources, etc.) in the network 1200. The Sensor Comm I/F Module 1213 may,for example, communicate with a sensor directly, via any one or more ofa variety of intermediate nodes, etc. For example, any of the examplecommunication discussed herein between a Mobile AP and a sensor system,etc., may be performed utilizing the Sensor Comm I/F Module 1213.

Though not shown in FIG. 12, a Mobile AP may also, for example, comprisea client communication interface module utilized to perform or managecommunication between the Mobile AP and any of a variety of clientdevices (e.g., user devices, etc.).

The example Mobile AP 1210 comprises a Data Collection Module 1215 thatis operable to manage the collection of sensor (and other) data. TheData Collection Module 1215 may, for example, operate to determineand/or implement a data collection plan as discussed herein at the nodelevel. For example, the Data Collection Module 1215 may utilize any orall of the example communication interface modules 1211, 1212, and 1213to perform desired communications. The Data Collection Module 1215 may,for example in various scenarios, operate to receive a data collectionplan, form a data collection plan (e.g., autonomously or in conjunctionwith other nodes, etc.), modify a data collection plan, etc. In anexample implementation, the Data Collection Module 1215 may operate inaccordance with the example method 800 of FIG. 8.

The example Mobile AP 1210 may also comprise one or more Applications1217. Such Applications may, for example, request and/or utilize sensordata that is collected by the Data Collection Module 1215. In an examplescenario, an Application 1217 may comprise an on-board application ofthe Mobile AP 1210 that operates to request and/or receive collecteddata from the Data Collection Module 1215.

The example Mobile AP 1210 may also comprise one or more Processors 1218and Memory Devices 1219. The Processor(s) 1218 may, for example,comprise any of a variety of processor characteristics. For example, theProcessor(s) 1218 may comprise one or more of a general purposesprocessor, RIS processor, microcontroller, ASIC, DSP, video processor,etc. The Memory Device(s) 1219 may, for example comprise any of avariety of memory characteristics. For example, the Memory Device(s)1219 may comprise a volatile memory, non-volatile memory, etc. TheMemory Device(s) 1219 may, for example, comprise a non-transitorycomputer-readable medium that comprises software instructions that whenexecuted by the Processor(s) 1218, cause the Mobile AP 1210 to performany or all of the functionality discussed herein (e.g., with regard tothe example methods 800 and 1100 discussed herein, etc.).

Note that the second Mobile AP 1220, the Fixed AP 1225, and/or any of avariety of network nodes may comprise configurations that share any orall aspects with the example Mobile AP 1210.

In general, the systems and methods presented herein, in accordance withvarious aspects of the present disclosure, adapt the rules (or strategyor plan) by which data is gathered. Such adaptability may, for example,be performed in a distributed fashion. For example, the determiningplans for collecting data as well as the actual collection of the datamay be performed in a distributed manner. In an example implementation,a combination of central control and distributed control of datacollection activities may be utilized. In an example implementation,control of data collection activities may be generally completelydistributed among the data collecting nodes themselves with a minimalamount of central oversight.

The manner in which data is collected may thus be optimized based on anyor a large number of considerations, for example regarding environment,network operation, overall context, individual node contexts, etc. Anyor all nodes of the system may provide information relevant to thecollection of data by the network nodes.

In a network implementation in accordance with various aspects of thepresent disclosure, a network of moving things may be utilized as aflexible and efficient backbone for sensor data communication. Such anetwork may provide the needs of any of a variety of organizations, forexample business enterprises, municipalities, infrastructure maintenanceorganizations, security organizations, etc.

In an example implementation, mobile-to-mobile communication links maybe utilized to share control information between nodes, to sharecollected data between nodes, to share storage, processing, and/orcommunication responsibilities for such collected data, etc.

In accordance with various aspects of this disclosure, examples of thenetworks and/or components thereof presented herein are provided in U.S.Provisional Application Ser. No. 62/222,192, titled “CommunicationNetwork of Moving Things,” filed on Sep. 22, 2015, which is herebyincorporated herein by reference in its entirety.

In accordance with various aspects of this disclosure, the networksand/or components thereof presented herein are provided with systems andmethods for integrating such networks and/or components with othernetworks and systems, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/221,997, titled “IntegratedCommunication Network for A Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for synchronizing such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,016, titled “Systems and Methods forSynchronizing a Network of Moving Things,” filed on Sep. 22, 2015, whichis hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,042, titled “Systems and Methods forManaging a Network of Moving Things,” filed on Sep. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for monitoring such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,066, titled “Systems and Methods forMonitoring a Network of Moving Things,” filed on Sep. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for detecting and/or classifying anomalies insuch networks and/or components, non-limiting examples of which areprovided in U.S. Provisional Application Ser. No. 62/222,077, titled“Systems and Methods for Detecting and Classifying Anomalies in aNetwork of Moving Things,” filed on Sep. 22, 2015, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing mobility in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,098, titled “Systems and Methodsfor Managing Mobility in a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing connectivity in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,121, titled “Systems and Methodsfor Managing Connectivity a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for collecting sensor data in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,135, titled “Systems and Methodsfor Collecting Sensor Data in a Network of Moving Things,” filed on Sep.22, 2015, which is hereby incorporated herein by reference in itsentirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for interfacing with such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,145, titled “Systems and Methodsfor Interfacing with a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for interfacing with a user of such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,150, titled “Systems and Methodsfor Interfacing with a User of a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for data storage and processing in such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,168, titled “Systems and Methodsfor Data Storage and Processing for a Network of Moving Things,” filedon Sep. 22, 2015, which is hereby incorporated herein by reference inits entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for vehicle traffic management in such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,183, titled “Systems and Methodsfor Vehicle Traffic Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for environmental management in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,186, titled “Systems and Methodsfor Environmental Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing port or shipping operation in suchnetworks and/or components, non-limiting examples of which are providedin U.S. Provisional Application Ser. No. 62/222,190, titled “Systems andMethods for Port Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing the accuracy of positioning orlocation information based at least in part on historical data,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/244,828, titled “Utilizing Historical Data toCorrect GPS Data in a Network of Moving Things,” filed on Oct. 22, 2015,which is hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing the accuracy of position or locationof positioning or location information based at least in part on theutilization of anchors, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/244,930, titled “Using Anchorsto Correct GPS Data in a Network of Moving Things,” filed on Oct. 22,2015, which is hereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing communication between applications,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/246,368, titled “Systems and Methods forInter-Application Communication in a Network of Moving Things,” filed onOct. 26, 2015, which is hereby incorporated herein by reference in itsentirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for probing, analyzing and/or validatingcommunication, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/246,372, titled “Systems and Methodsfor Probing and Validating Communication in a Network of Moving Things,”filed on Oct. 26, 2015, which is hereby incorporated herein by referencein its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for adapting communication rate, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/250,544, titled “Adaptive Rate Control for Vehicular Networks,” filedon Nov. 4, 2015, which is hereby incorporated herein by reference in itsentirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for reconfiguring and adapting hardware,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/273,878, titled “Systems and Methods forReconfiguring and Adapting Hardware in a Network of Moving Things,”filed on Dec. 31, 2015, which is hereby incorporated herein by referencein its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for optimizing the gathering of data, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/253,249, titled “Systems and Methods for Optimizing Data Gathering ina Network of Moving Things,” filed on Nov. 10, 2015, which is herebyincorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing delay tolerant networking,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/257,421, titled “Systems and Methods for DelayTolerant Networking in a Network of Moving Things,” filed on Nov. 19,2015, which is hereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for improving the coverage and throughput ofmobile access points, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/265,267, titled “Systems andMethods for Improving Coverage and Throughput of Mobile Access Points ina Network of Moving Things,” filed on Dec. 9, 2015, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for coordinating channel utilization, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/270,858, titled “Channel Coordination in a Network of Moving Things,”filed on Dec. 22, 2015, which is hereby incorporated herein by referencein its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for implementing a network coded mesh network in thenetwork of moving things, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/257,854, titled “Systems andMethods for Network Coded Mesh Networking in a Network of MovingThings,” filed on Nov. 20, 2015, which is hereby incorporated herein byreference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for improving the coverage of fixed access points,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/260,749, titled “Systems and Methods forImproving Fixed Access Point Coverage in a Network of Moving Things,”filed on Nov. 30, 2015, which is hereby incorporated herein by referencein its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing mobility controllers and their networkinteractions, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/273,715, titled “Systems and Methodsfor Managing Mobility Controllers and Their Network Interactions in aNetwork of Moving Things,” filed on Dec. 31, 2015, which is herebyincorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for managing and/or triggering handovers ofmobile access points, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/281,432, titled “Systems andMethods for Managing and Triggering Handovers of Mobile Access Points ina Network of Moving Things,” filed on Jan. 21, 2016, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing captive portal-related control andmanagement, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/268,188, titled “CaptivePortal-related Control and Management in a Network of Moving Things,”filed on Dec. 16, 2015, which is hereby incorporated herein by referencein its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for extrapolating high-value data, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/270,678, titled “Systems and Methods to Extrapolate High-Value Datafrom a Network of Moving Things,” filed on Dec. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing remote software updating anddistribution, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/272,750, titled “Systems and Methodsfor Remote Software Update and Distribution in a Network of MovingThings,” filed on Dec. 30, 2015, which is hereby incorporated herein byreference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing remote configuration updating anddistribution, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/278,662, titled “Systems and Methodsfor Remote Configuration Update and Distribution in a Network of MovingThings,” filed on Jan. 14, 2016, which is hereby incorporated herein byreference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for adapting the network, for exampleautomatically, based on user feedback, non-limiting examples of whichare provided in U.S. Provisional Application Ser. No. 62/286,243, titled“Systems and Methods for Adapting a Network of Moving Things Based onUser Feedback,” filed on Jan. 22, 2016, which is hereby incorporatedherein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing and/or guaranteeing data integritywhen building or performing data analytics, non-limiting examples ofwhich are provided in U.S. Provisional Application Ser. No. 62/278,764,titled “Systems and Methods to Guarantee Data Integrity When BuildingData Analytics in a Network of Moving Things,” Jan. 14, 2016, which ishereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing self-initialization and/or automatedbootstrapping of mobile access points, non-limiting examples of whichare provided in U.S. Provisional Application Ser. No. 62/286,515, titled“Systems and Methods for Self-Initialization and Automated Bootstrappingof Mobile Access Points in a Network of Moving Things,” filed on Jan.25, 2016, which is hereby incorporated herein by reference in itsentirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing power supply and/or utilization,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/295,602, titled “Systems and Methods for PowerManagement in a Network of Moving Things,” filed on Feb. 16, 2016, whichis hereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for automating and easing the installation and setupof the infrastructure, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/299,269, titled “Systems andMethods for Automating and Easing the Installation and Setup of theInfrastructure Supporting a Network of Moving Things,” filed on Feb. 24,2016, which is hereby incorporated herein by reference in its entirety.

Though various portions of this disclosure generally discussed thecollection of data from data sources, it should be readily understoodthat the scope of this disclosure also applies to the communication ofinformation to the data sources. For example, any or all of the networkcomponents discussed herein may be utilized to share collected databetween data sources, to communicate other data (e.g., control orconfiguration information, program update information, etc.) to the datasources (e.g., sensor systems, etc.), etc. Such reverse communicationmay also be incorporated into any or all aspects of the data collection(or communication) planning discussed herein.

In summary, various aspects of this disclosure provide systems andmethods for optimizing data gathering in a network of moving things. Asnon-limiting examples, various aspects of this disclosure providesystems and methods for operating sensor systems and collecting datafrom sensor systems in a network resource-efficient manner. While theforegoing has been described with reference to certain aspects andexamples, it will be understood by those skilled in the art that variouschanges may be made and equivalents may be substituted without departingfrom the scope of the disclosure. In addition, many modifications may bemade to adapt a particular situation or material to the teachings of thedisclosure without departing from its scope. Therefore, it is intendedthat the disclosure not be limited to the particular example(s)disclosed, but that the disclosure will include all examples fallingwithin the scope of the appended claims.

1-28. (canceled)
 29. A communication network mobile access point (MAP)comprising: a wireless transceiver; and at least one module comprising aprocessor and memory, wherein the at least one module is operable to, atleast: determine a data collection plan comprising a list of sensorsfrom which to collect data during a travel route; implement the datacollection plan while traveling along the travel route by, at least inpart, operating to utilize the wireless transceiver to collect sensordata while the MAP is traveling along the travel route; and whileimplementing the data collection plan, modify the list of sensors by, atleast in part, operating to: remove a sensor from which a second MAP hascollected data; and/or add a sensor from which a second MAP failed tocollect data.
 30. The MAP of claim 29, wherein the at least one moduleis operable to utilize the wireless transceiver to provide WirelessLocal Area Network (WLAN) Access Point services.
 31. The MAP of claim29, wherein the list of sensors comprises at least one sensor positionedat a fixed location.
 32. The MAP of claim 29, wherein the at least onemodule is operable to determine the data collection plan by, at least inpart, operating to negotiate with the second mobile access point. 33.The MAP of claim 29, wherein the at least one module is operable toreport information regarding the modified list of sensors to anothernetwork node.
 34. The MAP of claim 29, wherein the at least one moduleis operable to, while implementing the data collection plan: receiveinformation from the second MAP indicating that the second MAP failed tocollect data from the sensor; and based at least in part on the receivedinformation, add the sensor to the list of sensors.
 35. The MAP of claim29, wherein the at least one module is operable to, while implementingthe data collection plan: receive information from the second MAPindicating that the second MAP collected data from the sensor; and basedat least in part on the received information, remove the sensor from thelist of sensors.
 36. The MAP of claim 29, wherein the at least onemodule is operable to determine modify the list of sensors withoutapproval from a central controller.
 37. The MAP of claim 29, wherein theat least one module is operable to determine whether to modify the listof sensors by, at least in part, operating to interact with anautonomous vehicle control system.
 38. The MAP of claim 29, wherein theat least one module is operable to determine the data collection planby, at least in part, operating to receive the data collection plan froma central controller.
 39. A communication network mobile access point(MAP) comprising: a wireless transceiver; and at least one modulecomprising a processor and memory, wherein the at least one module isoperable to, at least: determine a data collection plan comprising alist of sensors from which to collect data during a travel route;implement the data collection plan while traveling along the travelroute by, at least in part, operating to utilize the wirelesstransceiver to collect sensor data while the MAP is traveling along thetravel route; and while implementing the data collection plan, at least:detect a condition comprising a vehicle condition, road condition, aweather condition, and/or a communication resource condition; and basedat least in part on the detected condition operate to modify the list ofsensors from which to collect data.
 40. The MAP of claim 39, wherein thedetected condition comprises a weather condition.
 41. The MAP of claim39, wherein the detected condition comprises a road condition.
 42. TheMAP of claim 39, wherein the detected condition comprises acommunication resource shortage condition.
 43. The MAP of claim 39,wherein the at least one module is operable to utilize the wirelesstransceiver to provide Wireless Local Area Network (WLAN) Access Pointservices.
 44. The MAP of claim 39, wherein the list of sensors comprisesat least one sensor positioned at a fixed location.
 45. The MAP of claim39, wherein the at least one module is operable to determine the datacollection plan by, at least in part, operating to negotiate withanother mobile access point.
 46. The MAP of claim 39, wherein the atleast one module is operable to determine modify the list of sensorswithout approval from a central controller.
 47. A communication networkmobile access point (MAP) comprising: a wireless transceiver; and atleast one module comprising a processor and memory, wherein the at leastone module is operable to, at least: determine a data collection plancomprising a list of sensors from which to collect data during a travelroute; implement the data collection plan while traveling along thetravel route by, at least in part, operating to utilize the wirelesstransceiver to collect sensor data while the MAP is traveling along thetravel route; and while implementing the data collection plan, modifythe list of sensors by, at least in part, operating to: adjust a dataresolution associated with a sensor of the list of sensors; and/oradjust a priority associated with a sensor of the list of sensors. 48.The MAP of claim 47, wherein the at least one module is operable tomodify the list of sensors by, at least in part, operating to adjust adata resolution associated with a sensor of the list of sensors.
 49. TheMAP of claim 47, wherein the at least one module is operable to utilizethe wireless transceiver to provide Wireless Local Area Network (WLAN)Access Point services.
 50. The MAP of claim 47, wherein the list ofsensors comprises at least one sensor positioned at a fixed location.51. The MAP of claim 47, wherein the at least one module is operable todetermine the data collection plan by, at least in part, operating tonegotiate with another mobile access point.
 52. The MAP of claim 47,wherein the at least one module is operable to determine modify the listof sensors without approval from a central controller.